To ensure a successful integration, we recommend you test your app using our sandbox server before requesting production access. Head over to our Developers page for more info at https://due.com/developers/. Be sure to utilize our Postman collections for simple examples.
Webhooks can be used to get notified about updates to your applications payments. Simply include a webhook_url, as an https url, when charging a card or customer. A POST request will be sent to that url when the payment status updates. The POST request will include the transaction id. Your server can then use the transaction id to get the latest transaction info and act accordingly.
Account Names and Soft Descriptors
When a charge appears on the cardholder's statement, it will be in the form WPY*. To avoid refunds, chargebacks, and any associated fees due to recognition issues, use payment account names which are easily recognizable.
Make sure you understand how Due's fees structure works. For more info go to our Payments page at https://due.com/payments/.
Throttle Limits & Batching Requests
In an effort to protect all our partners from poor performance, our system uses API throttling. Even the largest of partners rarely need their limits modified, but we do realize, under rare circumstances, exceptions must be made. If you feel you need a higher limit after testing reasonable use cases and implementing batch requests, we're happy to evaluate your specific situation. You can read more about this in the throttling and batch calls reference pages.
- Review any necessary PCI Compliance requirements.
- Create app account in production. Make sure all settings from your sandbox app account are migrated to your production app account. Add your KYC and Bank Account information.
- Email email@example.com and send us your sandbox and production app ids so we can migrate any administrative settings from sandbox to production.
- Get production app id from support.
- Switch endpoints from sandbox to production.