International credit cards are hereinafter referred to as Credit Card

Local payments are hereinafter referred to as APM

International Credit Card Payment

Prerequisites

1. Merchant has PCI qualification and has been verified by PingPongCheckout. (For PCI-DSS, please send email attachments to acquire-risk@pingpongx.com and CC gig-tech-acq@pingpongx.com)

2. Merchant has the capability to develop their own checkout system.

Note

This solution requires the merchant server to store and process cardholder credit card information, therefore it is mandatory that the merchant has PCI-DSS certification.

Interaction Flow

The following provides a brief explanation of the main steps

1. Step 1

   Initialize the risk control plugin after entering the merchant's checkout page

2. Step 2

   Listen to the card number input box, cardholder fills the card number, when the card number changes or the card number input box loses focus, trigger the initialization event - complexInit

3. Step 3

   In the complexInit event, the risk control plugin interacts with the PingPongCheckout server, returning the jsGeneratedData parameter

4. Step 4

   Client submits the order and jsGeneratedData parameter to the merchant server

5. Step 5

   Merchant server requests Order and Pay, submitting jsGeneratedData and other parameters together

6. Step 6

   PingPongCheckout server responds to the request result, deciding whether to enter the 3D process based on the return result

7. Step 7

   No 3D verification required, merchant can execute custom logic, display payment result

8. Step 8

   3D verification required

   1. Trigger the 3D verification event of the risk control plugin, the page will be redirected to the 3D challenge page, the cardholder needs to fill in 3D verification information
   2. Issuing bank verifies 3D information
   3. Issuing bank responds verification result to PingPongCheckout server
   4. Page is redirected to the payment result page filled in by the merchant

9. Step 9

   PingPongCheckout server pushes payment result, for how to obtain asynchronous notification messages, see Asynchronous Notification

API List

Order and Pay
Asynchronous Notification
Apply for Refund

Client Integration

Integrate Risk Control Plugin

End-to-end integration requires risk control JS to collect necessary information for transaction decision-making. When the cardholder completes entering the card number, the risk control plugin will call the PingPongCheckoutServer API to send card number data for verification,

See 3DS Integration Guide for details

Server Integration

Create Order and Pay

Request Order and Pay

Process Response

After requesting the transaction interface, PingPongCheckout responds based on request parameters, the merchant should handle the transaction according to the response. The processing result may be an intermediate state, requiring asynchronous notification integration to handle transaction status. Please go to Asynchronous Notification

Local Payment

Interaction Flow

The following provides a brief explanation of the main steps

1. Step 1

   Client places order

2. Step 2

   Merchant server requests Order and Pay

3. Step 3

   If the request is successful, PingPongCheckout's response result has 2 possibilities:

   • QR code: Follow the prompt, scan to pay
   • url: Jump to APM payment channel provider

4. Step 4

   Complete payment on the page specified by the APM channel

5. Step 5

   PingPongCheckout server pushes payment result, for how to obtain asynchronous notification messages, see Asynchronous Notification

6. Step 6

   After the merchant receives the notification, should return code 200

API List

Order and Pay
Asynchronous Notification
Apply for Refund

Server Integration

Create Order and Pay

Request Order and Pay

Client Integration

After successful server order placement, perform different operations based on the Order and Pay response parameters

Parameter	Description
paymentQrCode	Display QR code to complete payment
paymentRedirectUrl	Direct redirect