Go-live checklist

Check off these steps before launching your integration in production.

The following steps ensure you have a complete implementation.

Ensure that your business is PCI-compliant.

You must submit the Self-Assessment Questionnaire A to Dojo.

Contact Dojo to enable Virtual Terminal (VT) payments

As a Dojo customer, if your business is enabled for card-not-present (CNP) payments, you can set up your own virtual terminal with Dojo. To enable a virtual terminal in your account, contact Dojo customer support.

Ensure that your VT implementation is ready

You must have either a prebuilt checkout page or a checkout component ready alongside your complete VT implementation to start accepting payments.

Test in the sandbox

Before going live, test your integration in the sandbox. For each payment method that you offer:

Make a successful payment.
Make an unsuccessful payment.

Use the test card numbers below to make payments:

Card Name	Card number	Expiry Date	CVV	3D security	Status
Test Cardholder	5200 0000 0000 1005	12/24	020	No	Successful
Test Cardholder	5200 0000 0000 1096	12/24	020	2.0	Successful
Test Cardholder	4456 5300 0000 1013	12/24	341	No	Decline

note

When using a test card with 3D security (3DS), the virtual terminal will automatically skip all 3DS checks.

Handle 4xx and 5xx responses

For each integration, you need to make a call to our API. In cases API calls fail, you'll receive an error message with an HTTP status code and a traceId containing the unique identifier of the failing request. You should build some logic on your server to handle any errors. For example, you can handle them as exceptions.

Configure and test your webhooks

To test webhooks before you create or configure a live service, you can use one of several request logging sites, for example, WebHook Tester. Alternatively, use a service like ngrok.

Our webhooks provide "at least once" delivery of events. This means that you might get the same event several times. Your application needs to be built to handle those cases. You can detect duplicate events by comparing the id to previous events.
Make sure you're receiving all notifications you need for the integration.
Check URL you provide for notifications. It must be publicly accessible and be HTTPS as well.
Ensure you have set up webhooks in the live mode exactly as you did in the test.

You can manage webhooks in the Developer Portal or by using our API.

Switch API keys

Check that your integration doesn't cause your API keys to be publicly available.
Switch your secret key to production one with the prefix sk_prod_. If you haven't a production key, use the Developer Portal to create it.

Check the result

Make your first live API call to make sure that your production key is working. Follow the payment link you generated to see the result. For the production environment, there should be no yellow Sandbox label.