Accept credit and debit card payments by integrating with the checkout.

PCI Compliance

Note

Depending on your integration method, PingPongCheckout may require you to submit PCI DSS documentation before accepting credit card payments in the production environment.

Accepting credit and debit card payments requires compliance with PCI DSS requirements. See details in PCI DSS Compliance Navigation

Integration Method	PCI DSS
Embedded Checkout	Not Required
Redirect Checkout	Not Required
API	Required

Integration Navigation

Step1 Risk Control Component and 3DS Component Integration

See details in Dynamic 3D Secure

Step2 Request Order Creation and Payment

In the response of API Create Order and Pay:

1. When status is SUCCESS, the order has been paid.
2. When status is PROCESSING, the order has been created but not paid.
   1. bizContent.threeDContinue = false No 3DS verification required, you can wait for asynchronous notification.
   2. bizContent.threeDContinue = true, 3DS verification required, you need to redirect to the 3DS verification page.
3. When status is FAILED, order creation failed.

See details in International Credit Card Payment

paymentMethod
VISA
MasterCard
American Express
Discover
JCB
UPIPay

Immediate Capture and Manual Capture

By default, all credit card payments are captured immediately after authorization. Alternatively, you can set up manual capture. See details in Capture

Alert

Authorization is only valid for a limited time (generally 7 days). If an authorized payment is not captured or canceled, it will expire once the scheduled deadline is missed and will be automatically VOID.

3D Secure

• S2S integration requires you to embed risk control JS and 3DS components.
• If unable to embed JS components, please apply to business or risk control for API access to 3DS method.

1. Use PingPongCheckout's risk control system for automatic decision: We will automatically decide through the risk control system. When 3D Secure is required, it will automatically be decided as 3D Secure, and the checkout will automatically redirect to the 3D Secure page.
2. Custom decision: If you have your own risk control system and mature risk control experience, and need manual control of 3D Secure, you can use the executeThreeD parameter. See details in Dynamic 3D Secure

Alert

When using the custom decision function, if your acquirer processing entity and your customer's issuer processing entity are both in the European Economic Area (EEA), Monaco, your payment falls within the scope of PSD2 SCA. For this reason, you may need to set up 3DS verification for most transactions, except for TRA exemptions.