Skip to main content

Go-live checklist

Review Dojo's requirements and complete the necessary tests before launching your integration in production.

Risk and Compliance​

tip

As part of the application process, Dojo reviews the merchant's website to ensure it meets our security and legal requirements. To avoid delays, please ensure the merchant's website clearly displays all of the following information.

RequiredInformation
Contact detailsYour business’s address and either its email address or telephone number need to be included on your website. The footer or a ‘Contact us’ page is a good place to display this information.
Legal Entity NameThe legal name of your business must be included on your website and must match the name on your contract with Dojo. A ‘Contact us’ or ‘About us’ is a good place to put this information.
Refund policyYou must have a clearly labelled refund policy displayed on your website. This can either be a separate policy or included as a section in your terms and conditions.
Privacy policyYou must have a clearly labelled privacy policy displayed on your website. This can either be a separate policy or included as a section in your terms and conditions.
Card Scheme LogosYou must clearly display up-to-date logos for every card scheme your website accepts payments from. You can download logos here: Visa / Mastercard / American Express
Terms and ConditionsYour website’s terms and conditions must reference your business’s legal name, and it must be the same as that on your contract with Dojo. If your terms and conditions also contain your privacy policy and/or refund policy, these must be clearly labelled.
Secure Checkout PageYour checkout page must enable customers to access the card details page and enter their card details. It should also be secure. You can check this by seeing if there is a ‘padlock’ icon next to the URL in your web browser’s address bar.

End-to-end testing​

The following steps ensure you have a complete implementation.

1. 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.
  • Make a successful payment after an unsuccessful one to test that you update a client session secret.
  • Make a successful payment with 3DS.
  • Make an unsuccessful payment with 3DS.
  • Make a successful payment using any supported wallet payment methods

Use the following test card numbers to make payments:

Card NameCard numberExpiry DateCVV3D securityStatus
Test CardholderCopy
5200 0000 0000 1005Copy
12/29Copy
020Copy
NoSuccessful
Test CardholderCopy
5200 0000 0000 1096Copy
12/29Copy
020Copy
2.0Successful
Test CardholderCopy
4456 5300 0000 1013Copy
12/29Copy
341Copy
NoDecline

2. Handle errors​

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.

3. Test webhooks​

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.

4. Switch to production keys​

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.

5. Check the result​

Make your first live API call to make sure that your production key is working. Open your checkout page to see the result.

Last updated on