Recommendations & Best Practices
Integration Recommendations & Best Practices
Integration
- For Acceptance, ensure that the charge ID is passed in the Charges API based on the type of policy
- For Reconciliation purposes, ensure that the
reference.order
andreference.transaction
are passed via API/SDK - For handling Duplicate charges, use
reference.idempotent
- For Webhook Notification, use
post.url
within the API endpioints - For securing the Webhook Notification, use the hashstring calculation
- For finding the status of the payment for displaying on the confirmation screen, use Retrieve a Charge at the point of redirection
- Please process all refunds via API or Enterprise Dashboard
- For customized user access management write to [email protected] with required access
- For faster checkout experience use the card sdk v1/v2 instead of charge API
Before going live
- Ensure that your integration is thoroughly tested in sandbox and production
- Request an Integration Review call with the Developer Experience team at tap
- Ensure that the
sk_live
andpk_live
keys are used - Ensure that the
POST.URL
andREDIRECT.URL
are pointed to your production urls - Ensure that one live transaction is done for every payment method for all your integration channels (Web/Mob)
- Ensure that you are able to view the transactions in the Enterprise Dashboard as well in your system
Post go live
- Monitor the transactions using the Enterprise Dashboard
- For Payout reports, use the payout API or Enterprise Dashboard
Updated 7 months ago