This pages provides an overview of the main components of the sandbox environment including the payment page, dashboard, and API. The purpose is to provide enough information on the different integration options so you can begin the integration process with the epay3 payment platform.
The payment page is exactly the same as your production payment page except that this one only accepts fake transactions and never executes a debit on a real account.
The dashboard gives you a comprehensive view of all transactions run through your account.
The API provides an integration point to process transactions. By default, the API Url will present you with the Swagger UI which provides rich, interactive documentation.
Test Transaction Numbers
Swagger and SDK
When using the API, you may notice that the amount supplied and the amount that is shown in the dashboard differ. This is due to a customer fee being added as the transaction is being processed.
We have provided a C# SDK on Github that includes automated tests with sample code.
Token Page Sessions
While some of our clients choose to integrate directly with our API only, this does put some of the responsibility for security on the application developer since their system is actually capturing the credit card information. This is why we’ve added the option for a blended API integration where the user enters the sensitive payment information and the API is used to verify that the payment method was successfully saved (as described in the workflow below).
Via the API, generate a token page session Id by passing in any custom attributes to attach to the transaction and a success Url. The success Url is the location to which you would like the user forwarded once a payment method is successfully saved through the hosted page. The session Id returned by the API is valid for 30 minutes.
Using the API and the token Id from the query string, execute a GET operation against the API to obtain the token details including any custom attributes passed in during Step 1. This token Id can be used in subsequent API calls to execute transactions.