Create environments and access secrets

Create one environment and an access secret via the Spreedly web application.

This step is required before environment creation via API can begin.

  1. Environments, access secrets, and sub-merchants should follow a unique, consistent naming pattern for better organization. We recommend that the environment, sub_merchant, and access_secret follow the naming pattern below:
    • secret: secret_{environment_name}
    • environment: environment_{sub_merchant_name}
    • sub merchant: sub_merchant_{sub_merchant_name}

Create environments, environment-level access secrets and sub-merchant objects via the API [Optional]

  1. Create environments via the API or from our web application - This allows merchants and platforms to segment their business into individual, logical vaults at scale.
  2. Create single-environment access secrets via the API to create and associate credentials to environments through API actions. You can create and manage environments directly from the [Create Environment page]( Be sure to read up on Collect payment methods and set the environment to collect via iFrame payment form or leave it unrestricted.
  3. Create and associate sub-merchant objects via the API [Optional] - This API object allows the user— most commonly the platform—to associate representative identification data for each individual merchant, including name, URL, email, industry payment identifiers, and ad-hoc meta-data or internal identifiers that the aggregator is leveraging to associate to their merchants (e.g. UIDs). In addition to enhancing their own identification and transactional reporting capabilities, the aggregator can help themselves by helping Spreedly quickly isolate and identify impacted merchants when there are issues or support cases.