Payments for finance teams
Next steps
After the platform has completed sandbox integration and is ready to move to production, the next step is to complete a production readiness review with Xe. Production access should only be enabled after the integration has been demonstrated, required checks are complete, and Xe has created or enabled the production account and credentials.
Step-by-step production go-live process
- Complete sandbox integration and testing
The platform completes its API integration in the sandbox environment, including authentication, payment creation, validation, error handling, and any required webhook or callback handling. - Schedule a go-live review with Xe
The platform contacts Xe to arrange a call or demo session. The purpose of the session is to show that the integration works end to end and that the platform is ready to request production access. - Demo the integration to Xe
The platform walks Xe through the key user journeys, including customer selection, payment setup, quote or payment flow, confirmation, status handling, and failure scenarios where applicable. - Xe reviews the integration
Xe reviews the demo and may optionally review code, request sample API requests and responses, or ask for evidence that required test cases have passed. Any issues identified must be resolved before production enablement. - Confirm production readiness
The platform confirms that operational, technical, and support processes are ready. This includes production redirect URLs, security controls, monitoring, error handling, support contacts, and rollback or incident procedures. - Xe creates or enables the production account
Xe creates the production account, enables the required Pay API capabilities, configures applicable account settings, and confirms that production access is available. - Generate or receive production credentials
The platform generates or receives production credentials according to the agreed setup. Secrets must be stored securely and should only be accessible to authorised production systems and users. - Run production smoke tests
The platform and Xe complete limited production validation to confirm that authentication, account access, payment setup, and status handling work as expected in the production environment. - Go live and monitor closely
After Xe confirms readiness, the platform enables the production payment journey for users. The platform should monitor early activity closely and raise any issues through the agreed support path.
Production readiness checklist
15 items
Responsibilities
| Stage | Platform | Xe |
|---|---|---|
| Sandbox completion | Completes development, testing, and internal sign-off. | Provides documentation, sandbox access, and integration support where required. |
| Go-live demo | Schedules the review and demonstrates the end-to-end integration. | Reviews the integration and confirms any issues or required changes. |
| Production setup | Provides production configuration details, redirect URLs, contacts, and readiness confirmation. | Shares the App ID, creates or enables the production account, and configures required capabilities. |
| Credentials | Generates or stores production credentials securely and restricts access. | Enables the approved production credential process. |
| Smoke testing | Runs limited production validation and confirms expected behaviour. | Supports validation and confirms production readiness. |
| Launch | Enables the production journey for users and monitors early transactions. | Provides support during launch and helps investigate any production issues. |
What the platform should provide to Xe before production
- Confirmation that sandbox testing is complete.
- A demo of the completed integration or a walkthrough of the production journey.
- Production redirect URLs, callback URLs, or webhook endpoints, if used.
- Primary technical, operational, and escalation contacts.
- Expected launch date and go-live window.
- Expected transaction volumes, currencies, and payment use cases.
- Confirmation that secrets, credentials, and access controls are managed securely.
- Confirmation that customer onboarding and readiness checks are handled before payments are enabled.
Important
Sandbox credentials and production credentials are separate. Do not use sandbox keys, sandbox URLs, or test configuration in production. Payments should only be enabled after Xe confirms that the production account and required production access are ready.