📄️ Overview
Zamp Pay empowers merchants to accept crypto payments from customers - across chains, wallets, coins. In order to do so, merchants would need to integrate the Zamp Pay SDK.
📄️ Initiate Payment Session
In order to initiate a payment session, the merchant has to make an initiate call to Zamp. In return Zamp returns some key data points, which the merchant would need to store as well as pass on to their front end to initiate the Zamp SDK.
📄️ Get Payment Session
Endpoint//api.zamp.finance/payments/v1/payment-sessions/
📄️ Integrate JS SDK
In order to facilitate a seamless crypto acceptance flow for your end user, we request our merchants to integrate our SDK. The SDK can be added as an inline script in the HTML page.
📄️ Get Payment Session by Reference Id
Endpoint//api.zamplabs.com/payments/v1/payment-sessions?reference_id=
📄️ Refund
Endpoint//api.zamplabs.com/payments/v1/refunds
📄️ Get Refund By Id
Endpoint//api.zamplabs.com/payments/v1/refunds/
📄️ Get Refund By Reference Id
Endpoint//api.zamplabs.com/payments/v1/refunds/?reference_id=
📄️ Webhooks
Whenever a transaction is initiated, we update the merchant on the status of the transaction with the help of webhooks. Our on boarding team will share the IP Address from which webhook calls will be made to the merchants endpoints. We advice the merchant to whitelist only these IP Addresses from which legitimate calls from Zamp will be delivered.
📄️ Create payment links
You can programatically create easy to understand payment links which can be shared with the users to accept fiat payments. These payment links will be valid for 24 hours once the link is opened.
📄️ Get Merchant Payment Options
Endpoint//api.zamplabs.com/v1/payment-options
📄️ Payment Session Failure Codes
| Failure Code | Failure Reason |
📄️ Refund Failure Codes
| Failure Code | Failure Reason |