Non-hosted International Credit Card Payment
About 801 wordsAbout 3 min
2025-03-07
| Pay-in (Immediate Capture) | Authorization (Auth then Capture) | Partial Capture | Refund & Partial Refund | 记住卡号 | 重新支付 | CardOnFile | Recurring | 首笔0元 Recurring | 3DS |
|---|---|---|---|---|---|---|---|---|---|
Prerequisites
Merchant has PCI qualification and has been verified by PingPongCheckout. (For PCI-DSS, please send email attachments to
acquire-risk@pingpongx.comand CCgig-tech-acq@pingpongx.com)Merchant has the capability to develop their own checkout page.
Note
This solution requires the merchant's server to save and process the cardholder's credit card information, so it is mandatory that the merchant has PCI-DSS certification.
Interaction Flow
After entering the merchant's checkout page, initialize SafePayGuardJs and SecureShieldJs plugins
Initialize risk control plugins to prepare for subsequent operations
Listen to the card number input box, cardholder fills in the card number
When the card number changes or the input box loses focus, trigger the triggerThreeDsInit event in SecureShieldJs. The risk control plugin interacts with PingPongCheckout server and returns partial jsGeneratedData and browserInfo parameters
User clicks payment
Call the getGeneratedData method in SafePayGuardJs and SecureShieldJs to obtain risk control parameters
Client submits order information
Create order and pay, submit jsGeneratedData, browserInfo and other parameters collected from SafePayGuardJs and SecureShieldJs plugins together
PingPongCheckout server requests issuing bank interface
Send payment information to the issuing bank for processing
Issuing bank returns payment result to PingPongCheckout
Return result after processing payment request
PingPongCheckout server synchronizes request result
Receive and process the result returned by the issuing bank
Merchant client decides subsequent process based on returned result
Decide whether to enter 3D process based on bizContent.threeDContinue:
- No 3D verification required: Merchant can execute custom logic and display payment result
- Need to redirect to 3D verification: Redirect to 3D challenge page according to bizContent.threeDUnionParams.threeDRedirectUrl, after completion of verification PingPongCheckout will redirect to payResultUrl
API List
Client Integration
Integrate Risk Control Plugins
End-to-end integration requires risk control JS to collect necessary information for transaction decision-making. After the cardholder completes card number input, the risk control plugin will call PingPongCheckoutServer API to send card number data for validation,
See detailed 3DS Integration Guide
Server Integration
Create Order and Pay
Request Create 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 intermediate state, requiring asynchronous notification integration to handle transaction status. Please go to Asynchronous Notification
