Redirect to your URL using an iframe
You send a request via server-to-server You initiate a request to the payment gateway via server-to-server (S2S) communication. This takes place between your backend and Cryptadium.
Typically, the request contains the following data: Order details (amount, currency, description). Customer information (name, email, and other parameters if required).
Example request:
You receive a response with JSON payment details and a link to the payment form
After a successful request, Cryptadium sends you a JSON response with payment details. This response contains: Unique payment identifier. Details for the payment. A link to the payment form to be embedded on your page.
Example response:
You display the link on your page in an iframe
Once you have the payment link, you need to embed it into your page using the element. This will ensure that the payment form hosted by Cryptadium is displayed directly on your website.
Example of an embedded iframe:
You display the iframe with the payment form
When the customer visits your page to complete the payment, the iframe with the payment form is loaded and displays the page with the payment parameters (card, details, etc.). All the logic of interaction with the payment gateway happens inside the iframe, and you just provide the container for it. Payment completion, payment status and other details can be passed to you via the callback URL specified in your personal account settings.
Thus, iframe allows you to embed the payment process into your website without storing sensitive data on your server, while maintaining security and user-friendliness requirements.
Last updated