Available environments

Accounting as a Service provides different environments for you to integrate, test, and operate your systems. Each environment serves a specific purpose, helping ensure smooth operations from initial setup to full production use. You will start in the Sandbox environment, progress through the Test environment, and ultimately go live in the Production environment.

Available Environments

Sandbox Environment

The Sandbox environment is the initial environment for you to set up and test your integration with Accounting as a Service. It allows you to submit requests and receive notifications (such as EDI Error Sent) to ensure that your integration is working as expected.

  • Purpose: The Sandbox is used to set up your interfaces and test your connection with Accounting as a Service before moving to more advanced testing in the Test environment.
  • Usage: You will use the Sandbox to independently work on your integration, receiving direct feedback on your requests. Only after successfully submitting requests and receiving confirmation will you move to the Test environment.
  • Limitations: The Sandbox is a shared environment used by all clients, so the data and notifications are accessible to all users. Be cautious with sensitive data.

Base URL: https://api-uat.accounting.riverty.io
API Explorer: https://api-explorer-uat.accounting.riverty.io
Product: Sandbox Client

Test Environment

Once your requests have been successfully submitted and confirmed in the Sandbox, you will transition to the Test environment. The Test environment is configured specifically for you and mimics the real-world processes you will use in Production.

  • Purpose: The Test environment is for running full end-to-end tests (E2E), including external systems like PSPs, risk management providers, and settlement files.
  • Usage: This is where you will perform User Acceptance Testing (UAT), simulating real-world processes, including payments, returns, notifications, and more.
  • Limitations: In the Test environment, all processes are manually triggered rather than automated. You can choose to book self-service testing to automate this, if required.

Base URL: https://api-uat.accounting.riverty.io
API Explorer: https://api-explorer-uat.accounting.riverty.io
Product: Will be enabled when Sandbox-Testing is finished.

Production Environment

After successful testing and UAT sign-off, you will go live in the Production environment, where real customer transactions are processed.

  • Purpose: The Production environment handles all real-time operations, including payment processing, order management, returns, and notifications.
  • Usage: You’ll perform real transactions, with automated processes managing invoicing, dunning, and settlement files. Notifications and data updates occur on a daily basis.
  • Transition: Transition to Production is only possible after UAT sign-off and completion of the Go-Live checklist. You will need to subscribe to the Production environment and receive a new API key.

Base URL: https://api.accounting.riverty.io
API Explorer: https://api-explorer.accounting.riverty.io
Product: Will be enabled when UAT is signed off

Key Considerations

Data Privacy and Security

  • In the Sandbox, shared access to notifications means you should avoid using sensitive data.
  • In the Test and Production environments, your data is secure and available only to you. You can use production-like data during testing for realistic scenarios.

Notifications and Integrations

  • The Test environment includes the same notifications as Production, but they are triggered manually.
  • You will need to subscribe to the appropriate notifications (such as EDI Error Sent, Payment Received) to ensure everything is set up before moving to Production.

API Keys and Configuration

Each environment requires a separate subscription and API key. You will manage these keys through the API Explorer, ensuring that your requests are directed to the correct environment.