Server-to-Server Integration
Directly integrate your server with Curlec Payment Gateway using S2S Redirect, JSON V1, or JSON V2 APIs.
You can use Server-to-Server (S2S) payments integration to communicate directly with the Curlec servers and seamlessly integrate the service in your web application. You can capture payment details on your server and process the payments at your end. You have complete control over the look and feel of the payment experience for your customers.
Curlec supports two flavors of server-to-server integration. Choose the one that best suits your needs.
If you want more control over the way the customer is redirected, you can use the JSON API. You can decide where the customer should enter the transaction OTP to complete the payment - on your website or on the bank's page.
-
Handy Tips
While we have two JSON API versions, we recommend you to use V2 version. Using this API:
- Helps avoid multiple API calls.
- Provides a greater control over native OTP.
- Reduces payment timeout issues.
This is our default
. The payment creation request returns a variety of responses, which must be rendered on your customer's browser to proceed with the payment. These responses typically result in the browser being redirected to a bank or gateway page to complete payment authentication.PCI-DSS certification is required for all entities seeking to store, process, and transmit cardholder data.
Is this integration guide useful?
ON THIS PAGE