Module 5 - Production and Post-Live Transactions

Creating a Production Gateway or Receiver Token

Once you’ve thoroughly tested your integration and are ready to handle production traffic, you can switch to production by using your production credentials. To create a gateway or receiver token, set the sandbox flag to false and use the environment key and access secret for the environment you intend to process transactions in. Be sure to update all related code, including your iFrame and API credentials, to point to your production environment. If using Composer, ensure the workflow sandbox mode box is not checked and all gateways in your workflow are also your production gateways.

Tip: We highly recommend setting up a separate environment exclusively for production. This approach helps to keep your test and production data distinct, offering a cleaner and more organized experience on the Spreedly App dashboard.

By the end of this module:

• You will understand how to create a gateway token or receiver token.
• You will understand how to access data and reporting the Spreedly App.

Analyzing Data & Reporting

To explore reporting features in the Spreedly App, select "Reports" under the Performance section in the sidebar menu. Here, you can view shortcut summaries of common reports, including:

• Success Rates

• Failures

• Transactions

These reports are available for each environment, enabling you to analyze transaction performance and identify any issues.

Adding Users to Your Organization

In Module 1, you may have added users to your organization to grant access to features such as reporting, transaction viewing, and environment creation. We recommend having multiple users in your organization to better manage access.

When adding users, you can configure role-based access controls (RBAC). This enhances your organization’s security, defines clear roles, and ensures that users can only access the features relevant to them. Whether users are on the business or technical side of your use case, RBAC helps streamline the experience by limiting their access scope.

Additional Features

While the onboarding modules cover the basics of configuring your Spreedly account and processing production transactions, Spreedly offers many additional features to enhance your integration. If you've already enabled any of these features, refer to the following Help Center Articles for further guidance:

• Spreedly’s 3DS Global Solution

• Spreedly’s Advanced Vault

• Spreedly’s Transaction Recover

• Spreedly’s Protect

Though we've mostly focused on credit card transactions, Spreedly also supports a range of Alternative Payment Methods. Explore these options to offer your customers a checkout experience tailored to their needs. 

Need Help?

If you have questions about your integration, please reach out to our Support Team. For inquiries related to specific transactions, make sure to include the following information in your support request:

• The organization name associated with your Spreedly account

• A detailed summary of the issue or question

• Troubleshooting information (if applicable), such as:

  • Gateway/Endpoint being used

  • Transaction, Payment Method, and/or Gateway Token(s)

  • Error codes (Transaction Error or HTTP Status Code)

  • Steps to reproduce the issue

For customized, hands-on support with your Spreedly solution, our Implementation Team provides Architectural Reviews as a service to assist you in ensuring that everything is set up correctly and that you're maximizing the benefits of Spreedly as your payments orchestration solution. Contact your Account Manager for more details and pricing.

Module Completion

You have successfully completed Module 5 if you have:

• You have created a gateway token or receiver token.
• You have reviewed your reports in the Spreedly App.