1. Test End-to-End Flow

Ensure that merchant have tested the integration in the QA/ Sandbox environment for both successful & failure scenarios. Perform an end-to-end test simulation and make sure merchant integration is working fine for all the workflows that merchant have selected. Check if merchant have performed the following steps:

Product Workflows	Success Scenarios	Failure Scenarios
For Headers • Check the BD-Traceid is unique for the day and BD-Timestamp is passed correctly • Check "Content-Type" is passed as "application/jose". • Check "Accept" is passed as "application/jose"
For BillDeskNeo – Full Redirect • Create Order from the backend application for all flows (one-time payment, mandate setup etc.). Success and failure scenarios are handled. • Check orderid uniqueness. • Transaction response is handled properly in case of success and failure scenarios.
For CX+ – Deep API - One time payments • Create & Update Transaction API from the backend application for all flows (one-time payment, token provisioning etc.). Success and failure scenarios are handled. • Check orderid uniqueness. • Create & Update Transaction response is handled properly in case of success and failure scenarios.
For CX+ – Deep API - Recurring payments • Create & Update Transaction API with mandate object from the backend application for all flows (recurring payment). • Check orderid uniqueness. • Check Create Invoice API for both success and failure scenarios. • Create & Update Transaction with mandate setup response is handled properly in case of success and failure scenarios. • Create Mandate API from the backend application • Update Mandate API from the backend application

Please click here to access the test cases sheet that you need to self certify before going live with BillDesk.

2. Whitelist Production IPs/Domain

This integration will require whitelisting of merhcant's IPs/ domain used to open the checkout page. BillDesk will block if in case, any other domain is used to open the checkout page.

3. Configure Production Endpoint

Make sure merchant have configured/ replaced the endpoints to the production endpoints before going live.

4. Setup Production Keys

Ensure that the keys provided by BillDesk for accessing production environment are configured properly at merhcant's end. Make sure keys meant for encryption & signing of requests are properly handled at merhcant's end. Do not use encryption key for signing the request and otherwise.

5. Setup Webhooks

Ensure that merchant have set up and tested their Webhooks in the production mode for the events they want to receive notifications for.