PingPong

PingPong Checkout: Overview For Merchants
PingPong Checkout is the online payments solution from PingPong that lets merchants accept cards and alternative payment methods across global markets through a single integration. PingPong focuses on cross-border acceptance, tokenization for saved cards, recurring billing, and built-in risk tooling. Merchants can integrate via hosted checkout, embedded SDK, or direct server-to-server APIs and extend to in-person payments with a terminal API. PingPong supports settlement cycles set by contract and provides SFTP reporting for reconciliation.
Where PingPong Fits For Merchants
PingPong is a fit when you need:
-
Cross-border acceptance across APAC, Europe, and the Americas.
-
Multiple integration options that match your PCI scope and engineering capacity.
-
Card-on-file, subscriptions, and payment links for invoice-style or remote checkout.
-
Risk controls that include dynamic 3D Secure and dispute APIs.
-
Statement files and SFTP access for finance and reconciliation workflows.
Supported Payment Methods And Currencies
PingPong supports the major global card schemes alongside a large catalog of local payment methods and digital wallets.
-
Cards: Visa, Mastercard, American Express, UnionPay, Diners Club, JCB.
-
Wallets and Pay Buttons: Apple Pay and Google Pay.
-
Local APMs: Coverage spans Asia, Europe, and Latin America with methods such as PromptPay (TH), FPX and DuitNow (MY), BLIK and Przelewy24 (PL), Bancontact (BE), Trustly (EU), Konbini and Pay-easy (JP), OXXO and SPEI (MX), PIX (BR), GCash and Dragonpay (PH), GrabPay (SEA), Klarna and Afterpay for BNPL, and many more.
-
Checkout currencies: PingPong lists 50+ acceptance currencies for PingPong Checkout.
You also get in-person acceptance options via a Terminal API for card and QR-based payments, useful for omnichannel scenarios.
Key Capabilities
Card On File And Tokenization
-
Create tokens at checkout to support stored credentials and faster repeat purchases.
-
Use card-on-file flows to bind cards during an authorization or via verification.
-
Maintain token-to-customer mappings and pay later with the token through APIs.
Subscriptions And Recurring Billing
-
First transaction captures authorization and creates the mandate token.
-
Subsequent charges are initiated server-to-server on the agreed schedule.
-
Recurring parameters include start date, interval unit and count, and end date.
Order Lifecycle Controls
-
Capture: Automatic capture by default; manual capture is available through a dedicated API.
-
Void: Cancel uncaptured authorizations when needed.
-
Refund: Full and multiple partial refunds are supported, with idempotency controls.
Payment Links
-
Generate a hosted payment link from the merchant portal to collect one-off payments without doing a site integration. Availability is by enablement.
Disputes API
-
Programmatically fetch retrieval and chargeback details, upload evidence, and submit representments. Events and statuses are delivered by webhook to automate handling.
Reconciliation And Reporting
-
Settlement cycles can be configured as T+N, weekly, or on a specific month day.
-
Finance teams can pull settlement and transaction statements from an SFTP endpoint. File paths and statement formats are documented.
Sandbox And Test Resources
-
A sandbox environment exists with sample accounts and method coverage for integration testing.
Risk, Authentication, And Security
Dynamic 3D Secure
-
PingPong’s risk engine decides when to invoke 3DS based on cardholder behavior and rules.
-
You can override with merchant-level parameters to force, delegate, or skip per contracted profile.
Client-Side Risk Components
-
SecureShieldJs and related components add device signals and browser data to improve fraud screening for card transactions.
PCI Considerations
-
Hosted checkout or plugin: card data stays in PingPong’s environment, reducing your PCI exposure.
-
Embedded SDK: renders payment elements while isolating sensitive data.
-
Server-to-server: gives you maximum UI control but requires full PCI DSS compliance for card data handling. PingPong documents the requirements and verification steps.
Integration Options And Plugins
You can choose among:
-
Hosted Redirect Checkout: fastest route to go live with minimal engineering.
-
Embedded JavaScript SDK: show a unified payment list in your page with limited front-end work.
-
Server-to-Server APIs: full control over the checkout UI and flows.
-
Plugins for open-source platforms: Magento 2, WooCommerce, PrestaShop, OpenCart, and Zen Cart, with version guidance.
PingPong also references SaaS platform integrations for Shopify, Shopline, and Shoplus in its documentation.
Settlement, Funding, And Reconciliation
-
Settlement cycles are contract-based and can be configured as T+N, weekly, or monthly with matching statement cadence.
-
SFTP reporting provides compressed files for daily or periodic retrieval.
-
Time zone for statement generation is UTC+0 in the docs.
Coverage And Cross-Border Scope
-
Documentation sections outline country coverage across APAC, Europe, and the Americas.
-
PingPong’s global site lists acceptance of 170+ payment methods and 50+ checkout currencies, with local account and payout capabilities in additional markets.
Note that availability varies by vertical and region; enablement is subject to contracting and underwriting.
PingPong: Frequently Asked Questions (FAQs)
What is PingPong Checkout?
PingPong Checkout is the online payments solution from PingPong that lets merchants accept cards and alternative payment methods through a single integration across global markets.
Which payment methods and wallets does PingPong support?
PingPong supports major card schemes plus Apple Pay, Google Pay, and a wide catalog of local methods across APAC, Europe, and the Americas. Availability depends on your contract and region.
Which integration options does PingPong offer?
Hosted redirect checkout, embedded JavaScript SDK, server to server APIs, and plugins for Magento 2, WooCommerce, PrestaShop, OpenCart, and Zen Cart. SaaS platform options include Shopify, Shopline, and Shoplus.
How does PCI scope differ by integration mode?
Hosted checkout and plugins keep card data in PingPong systems which reduces your PCI exposure. The embedded SDK isolates sensitive fields. Server to server processing requires full PCI DSS compliance on the merchant side.
Does PingPong support tokenization and card on file?
Yes. Tokens can be created at checkout or via card verification, then used for repeat payments with server to server APIs.
Can I run subscriptions or recurring billing?
Yes. The first transaction sets up the mandate token. Subsequent charges are initiated on the defined schedule using server to server APIs.
How are capture, void, and refund handled?
Automatic capture is default and manual capture is available. You can void uncaptured authorizations and issue full or multiple partial refunds via API.
How does PingPong handle disputes?
A Disputes API lets you retrieve cases, upload evidence, and submit representments. Webhooks deliver dispute events and status updates.
What settlement cycles and reconciliation reports are available?
Settlement can be configured as T+N, weekly, or monthly. Finance teams can pull transaction and settlement statements via SFTP for reconciliation.
Does PingPong offer in person payments for omnichannel?
Yes. A Terminal API supports in person card and QR based acceptance to complement online checkout.
Is public pricing available?
No public fee tables are listed. Pricing, settlement cycles, and product enablement are contract based.
Is there a sandbox for testing?
Yes. A sandbox environment with sample accounts and methods is available for integration testing.
Where is PingPong available?
Documentation shows coverage across APAC, Europe, and the Americas with 170+ payment methods and 50+ checkout currencies. Actual availability depends on industry and underwriting.
Can I collect payments with payment links?
Yes. You can generate hosted payment links from the merchant portal for one off payments subject to enablement.