{"id":483,"date":"2024-08-08T19:43:08","date_gmt":"2024-08-08T19:43:08","guid":{"rendered":"https:\/\/lddpay.com\/?post_type=docs&p=483"},"modified":"2025-04-26T06:37:02","modified_gmt":"2025-04-26T06:37:02","password":"","slug":"s2s-card","status":"publish","type":"docs","link":"https:\/\/lddpay.com\/zh\/docs\/s2s-card\/","title":{"rendered":"S2S CARDPAY"},"content":{"rendered":"

S2S CARDPAY<\/h1>\n\n\n\n

Version: 5.3.2
Released: 2025\/03\/01<\/p>\n\n\n\n

Copyrighted by lddPay<\/p>\n\n\n\n

Introduction<\/h2>\n\n\n\n
\n\n\n\n

This document describes integration procedures and POST protocol usage for e-commerce merchants.<\/p>\n\n\n\n

S2S CARDPAY protocol implements acquiring payments (purchases) with specific API interaction using.<\/p>\n\n\n\n

\u26a0\ufe0f Pay attention<\/strong><\/p>\n\n\n\n

\n

To work with S2S CARDPAY protocol, merchants are required to comply with the Payment Card Industry Data Security Standards (PCI DSS).<\/em><\/p>\n<\/blockquote>\n\n\n\n

Integration process<\/h2>\n\n\n\n
\n\n\n\n

Merchant registration<\/h3>\n\n\n\n

Before you get an account to access Payment Platform, you must provide the following data to the Payment Platform administrator.<\/p>\n\n\n\n

Data<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
IP list<\/td>List of your IP addresses, from which requests to Payment Platform will be sent<\/td><\/tr>
Callback URL<\/td>URL which will be receiving the notifications of the processing results of your request to Payment Platform.
It is mandatory if your account supports 3D-Secure. The length of Notification URL should not be more
than 255 symbols.<\/td><\/tr>
Contact email<\/td>Email address of Responsible Person who will monitor transactions, conduct refunds, etc.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

With all Payment Platform POST requests at Notification URL the Merchant must return the string OK if he\/she successfully received data or return ERROR.<\/p>\n\n\n\n

\u26a0\ufe0f Pay attention<\/strong><\/p>\n\n\n\n

\n

Note that the notification URL may be temporarily blocked due to consistently receiving timeouts in response to the callback. If five timeouts accumulate within five minutes for a merchant\u2019s notification URL, it will be blocked for 15 minutes. During this block, all merchants associated with the URL will not receive notifications. The block automatically lifts after 15 minutes. Additionally, it is possible to manually unblock the URL through the admin panel by navigating to Configuration \u2192 Merchants \u2192 Edit Merchant. In this case, the block will be removed immediately. The timeout counter resets if a callback response is successfully processed. For instance, if there are four timeouts within five minutes but a successful response on the sixth minute, the counter resets.<\/em><\/p>\n<\/blockquote>\n\n\n\n

You should get the following information from administrator to begin working with the Payment Platform.<\/p>\n\n\n\n

Data<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
CLIENT_KEY<\/td>Unique key to identify the account in Payment Platform (used as request parameter). In the administration platform this parametercorresponds to the Merchant key field<\/td><\/tr>
PASSWORD<\/td>Password for Client authentication in Payment Platform (used for calculating hash parameter). In the administration platform this parameter corresponds to the Password field<\/td><\/tr>
PAYMENT_URL<\/td>URL to request the Payment Platform<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Protocol Mapping<\/h3>\n\n\n\n

It is necessary to check the existence of the protocol mapping before using the S2S integration. Merchants can\u2019t make payments if the S2S CARDPAY protocol is not mapped.<\/p>\n\n\n\n

Interaction with Payment Platform<\/h3>\n\n\n\n

For the transaction, you must send the server to server HTTPS POST request with fields listed below to Payment Platform URL (PAYMENT_URL). In response Payment Platform will return the JSON (http:\/\/json.org\/<\/a>) encoded string.<\/p>\n\n\n\n

3DS features<\/h4>\n\n\n\n

If your account supports 3D-Secure and credit card supports 3D-Secure, then Payment Platform will return the link to the 3D-Secure Access Control Server to perform 3D-Secure verification. In this case, you need to redirect the cardholder at this link. If there are also some parameters except the link in the result, you will need to redirect the cardholder at this link together with the parameters using the method of data transmitting indicated in the same result.<\/p>\n\n\n\n

In the case of 3D-Secure after verification on the side of the 3D-Secure server, the owner of a credit card will come back to your site using the link you specify in the sale request, and Payment Platform will return the result of transaction processing to the Notification URL action.<\/p>\n\n\n\n

\u26a0\ufe0f NOTE:<\/strong><\/p>\n\n\n\n

\n

As per our API for any 3DS transaction after request, we send to merchant response with:<\/p>\n\n\n\n

\n