# LLM Documentation This file contains links to all documentation sections. ## Table of Contents ### Tools - [Signature Tool](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/tools/sign/index.md): The signature tool is used to generate signatures that comply with the PingPongCheckout v4 signature specification. It is suitable for all developers who need to upgrade to version v4, ensuring that all parameters participate in the signature process. Following the new signature rules can guarantee the security and integrity of requests. - [JS-SDK Debug Tool](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/tools/sdk/index.md): The JS-SDK debug tool is used to simplify the debugging process of PingPongCheckout API. It supports accepting bizContent parameter in JSON object or JSON string format, making it convenient for developers to test and verify according to document requirements during development, ensuring the accuracy of parameter passing. - [Hosted-Redirect Debug Tool](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/tools/redirect/index.md): The Hosted-Redirect debug tool is used to simplify payment process debugging. It supports accepting the bizContent parameter as either a JSON object or JSON string, with automatic format conversion. It is suitable for development phase to ensure accurate parameter passing. Please strictly follow the documentation when passing values to ensure smooth debugging process. - [RiskDefense Debug Tool](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/tools/RiskDefense/index.md): The RiskDefense debug tool is used to test and verify the functionality of risk control plugins. It is suitable for developers to debug when integrating risk control systems, ensuring that rule configurations are correct and responses meet expectations. It supports simulating multiple transaction scenarios to help identify potential risks and optimize risk control strategies. - [Payment Request Tool](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/tools/request-tool.md) ### Appendix - [Country Codes](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/countryCode/index.md): The country or region code list provides two-letter codes for countries worldwide. It is suitable for scenarios requiring standardized country identifiers, such as international payments, logistics, and data exchange. The list covers multiple countries and regions from Afghanistan to the Central African Republic, ensuring accurate use of country codes in cross-border business. - [Transaction Currency](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/transactionCurrency/index.md): The transaction currency list provides detailed information about multiple global currencies, including currency names, three-letter codes, and decimal places for minimum units. Suitable for payment systems or financial applications that need to handle multi-currency transactions, ensuring accurate representation of currency amounts in international payments. - [Issuer Response Codes](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/actionCode/index.md): Issuer response codes list various response codes that may be encountered during payment processing, including response codes from Discover, Visa, and Mastercard. These codes are used to explain why transactions are accepted, rejected, or require further processing, helping merchants and technical personnel quickly identify issues and take appropriate actions. - [Currency Exchange Support](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/exchange/index.md): Currency exchange support lists the available currency pairs for conversion. This table applies to scenarios requiring international currency exchange, covering conversions between various major currencies from AED to JPY, helping users understand supported currency types and exchange directions, facilitating cross-border transactions and fund management. - [Sanctioned Countries List](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/sanctionedCountries/index.md): The sanctioned countries list provides information about countries and regions under international sanctions, including Chinese names and two-letter country codes. It is applicable to payment, trade, and other business scenarios that need to comply with international sanctions regulations. Please note that the regions of Crimea, Donetsk, and Luhansk, although part of Ukraine, are sometimes mentioned separately. - [Status Codes](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/successCodeList/index.md): The status code documentation lists return codes and their descriptions for various operations in the payment system, applicable to scenarios such as request processing, transaction status, and configuration validation. Success statuses include transaction success (000000) and request success (001000), while exceptions include merchant disabled (101000), parameter errors (102000), etc., helping developers quickly identify issues and optimize integration. - [disputes API Enumerations Description](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/chargebackReasonCode/index.md): Lists enumerations related to dispute handling, including chargebackStatus, CBReasonCodeEnum, CBDocTypeCodeEnum, and CBRequirementLevelEnum. These enumeration values define different states, reasons, required supporting material types, and their mandatory attributes for disputes, applicable in payment dispute management and handling processes, helping developers accurately - [Document Update Record](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/docUpdateRecord/index.md): The document update record lists the payment API and SDK updates for each month of 2025, including new API endpoint addresses, optimized unified order and face-to-face payment interface parameters, additional WeChat Mini Program payment response parameters, and enhanced embedded SDK functionality. - [Thailand Refund Bank List](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/XenditRefundBankList/index.md): The Thailand Refund Bank List provides bank codes and names that support refund services in Thailand. It is applicable for processing refund transactions in the Thailand region, covering major commercial banks and some international bank branches, ensuring accurate bank information in the refund process. - [GpayBankCode](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/GpayBankCode/index.md): GpayBankCode provides a code table of major Vietnamese banks, including bank names, bank codes, and Pin Bank codes. Suitable for scenarios that require identifying or validating Vietnamese bank information in payment systems. - [State Code Table for United States and Canada Regions](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/stateCode/index.md): This document provides Chinese names, English names, and corresponding codes for states and regions in the United States and Canada. It is applicable to scenarios requiring identification or validation of these regional information in payment systems, such as address entry, logistics delivery, etc. - [Language Codes](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/languageCode/index.md): The language code list provides multiple languages and their corresponding regional locale identifiers and API transmission values, used to unify language settings in multilingual environments. The table lists regional variants of major languages including German, English, Spanish, French, Italian, and Japanese, along with their corresponding API parameter values, making it convenient for developers to select appropriate language versions based on user location. - [CodeGrant](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/codeGrant/index.md): CodeGrant is a local payment Tokenization solution that authorizes payments through user identity verification, widely used in e-commerce and mobile payments. It is suitable for supporting e-wallet binding and subsequent payment operations, ensuring secure and convenient transactions. ### Technical Terms - [accId](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/accId/index.md): accId is the PingPong merchant shop number, serving as the unique identifier for merchants on the PingPongCheckout platform. This identifier can be obtained after completing PingPong merchant registration, and registered users can view it by logging into the merchant backend. - [Authorization](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/Authorization/index.md): Authorization (pre-authorization) is the first step in credit card payment processing, used to verify credit card validity and temporarily freeze a certain amount in the account. Applicable to e-commerce, in-app, and point-of-sale payment scenarios. Implemented through API calls, key steps include transaction initiation, sending authorization requests to the issuing bank, processing requests, and returning authorization responses. Pre-authorization is typically valid for 7 days and automatically VOIDs upon expiration. - [clientId](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/clientId/index.md): clientId is the unique identifier for PingPong merchants in PingPongCheckout. After completing PingPong merchant registration, you can obtain this ID by logging into the merchant backend and accessing the account center, which is used to identify and manage merchant information. - [Capture](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/Capture/index.md): Capture refers to the formal transfer of authorized funds from the shopper's account to the merchant's account. By default, payment authorization is automatically captured immediately after authorization. Many payment methods support separate authorization and capture, allowing for delayed capture, manual capture, or partial capture, and authorization can be canceled. Capture, along with void and refund, is classified as operations that modify payment status. - [Void](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/Void/index.md): Void refers to pre-authorization cancellation, used when merchants decide to reject an authorized but uncaptured payment. Applicable in cases such as detecting high-risk fraud. Once a payment has been successfully captured, it can no longer be canceled through VOID, and refunds must be processed to return the funds to the consumer. - [groupId](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/groupId/index.md): groupId is the unique identifier for groups in the merchant backend website management. In the group management page, you can obtain the groupId under the group name by creating or selecting an existing group and viewing details. Each group can be associated with multiple accIds. - [PCI Compliance Navigation](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/PCI/index.md): PCI compliance navigation defines the Payment Card Industry Data Security Standard (PCI DSS), ensuring that companies processing cardholder data maintain secure environments. Applies to all entities accepting credit cards or participating in payment processing, such as merchants, banks, and service providers. Obtaining PCI certification requires compliance with PCI DSS standards, completing self-assessment questionnaires or external audits, and conducting regular security scans. Integration methods include using PingPongCheck - [salt Retrieval](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/salt/index.md): salt serves as the merchant key for PingPong, used to verify PingPongCheckout API calls. After registration is completed, merchants can log in to the backend to view and manage their salt in Key Management. If a key leak is discovered, a new key can be generated using the refresh function to ensure security. - [transactionId](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/transactionId/index.md): transactionId is a string or number used to uniquely identify a transaction, ensuring the security and correctness of online transactions and peer-to-peer transfers. In PingPongCheckOut, transactionId specifically refers to the PingPong transaction serial number, suitable for tracking and managing transaction processes. - [Card Holder](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/cardHolder/index.md): A card holder refers to a shopper who uses cards issued by banks for cashless payments. This term applies to individuals or business users who complete transactions through bank cards in various payment scenarios. Understanding this concept helps in better designing and optimizing payment processes and related services. - [Card networks (or Card schemes)](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/CardNetworks/index.md): Payment networks define the standards for card issuance and transaction processing, ensuring that card issuers and acquirers operate within the same system. Major global payment networks such as Visa, Mastercard, American Express, and UnionPay not only provide necessary technical support, but also determine various transaction costs including interchange fees. - [CardNumber (PAN)](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/CardNumber/index.md): CardNumber (PAN) refers to the unique number on a payment card used to identify each card and reference it in transactions. The first six or eight digits form the Bank Identification Number (BIN), which helps identify the issuing institution. Cards may also contain security codes to support the security of off-site transactions. - [CardOnFile (CoF)](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/CardOnFile/index.md): CardOnFile (CoF) is a technology that stores card details to simplify the checkout process for returning customers, suitable for one-click payments, pay-per-use services, or recurring payments on irregular schedules. If merchants meet PCI Level 1/2 compliance, they can store card information themselves. - [NetworkToken](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/networkToken/index.md): Network tokenization is a service provided by Visa, Mastercard, etc., that replaces primary account numbers with 16-digit tokens to enhance payment security. Using network tokens can improve authorization rates, reduce shopper friction, and protect each transaction with one-time passwords. Even if cards are reissued after expiration or loss, the original tokens remain valid. Currently PingPongCheckout does not support direct collection of network tokens, but allows using existing tokens for - [Cards](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/Cards/index.md): Cards are plastic cards issued by banks to enable cashless payments. Including debit cards, credit cards, and prepaid cards, transactions are verified through information such as card numbers and security codes. Cards are widely used for point-of-sale transactions, e-commerce websites, and in-app payments, and can be linked to digital wallets to support cash withdrawals and online payments. - [Tokenization](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/Tokenization/index.md): Tokenization is a data protection technology that converts sensitive information such as credit card numbers into randomly generated strings (tokens) to enhance the security of payment systems. This technology uses tokens instead of real card numbers to process payments when users make transactions through payment gateways, preventing the leakage of sensitive information. Main advantages include improved security, simplified compliance, enhanced customer trust, and support for multiple payment scenarios. International credit cards and - [Failure Final State](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/FailureFinalState/index.md): Failure Final State is a transaction status flow pattern where the order status becomes final after payment failure and cannot be paid again. A new order number is required to initiate payment again. Suitable for scenarios requiring strict control of duplicate payments. Main states include SUCCESS, CLOSED, FAILED, PROCESSING, and INIT. - [Disputes](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/disputes/index.md): A dispute refers to the process where a cardholder raises an objection to a transaction, involving communication and negotiation between the cardholder, issuing bank, acquiring bank, and merchant. The dispute handling stage is relatively flexible, resolving objections through initial communication; if unresolved, it may escalate to a chargeback, resulting in transaction reversal and significant impact on the merchant. - [Chargebacks](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/chargebacks/index.md): Chargebacks are a formal transaction reversal mechanism where the issuing bank forcibly deducts the transaction amount from the merchant's account and refunds it to the cardholder after disputes cannot be resolved through initial communication. Used for handling cardholder objections to transactions, involving dispute escalation, chargeback notifications, merchant responses, and arbitration steps. The chargeback timeline is 180 days for cardholders to initiate chargebacks and 90 days for merchants to respond. - [Notification of Chargeback](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/NotificationOfChargeback/index.md): Notification of Chargeback (NoC) is a notification initiated by the issuing bank to inform the merchant that there is a dispute regarding a transaction. The NoC can be initiated after an information request, or directly after the transaction status is set to settled or refunded. Once the NoC is initiated, the dispute resolution process begins and funds will be deducted from the merchant's account. This applies to card transactions worldwide, with key steps including initiation. - [Pre-Arbitration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/PreArbitration/index.md): Pre-arbitration is a critical stage in the credit card transaction dispute resolution process, designed to resolve disputes through further evidence exchange and communication before formal arbitration. It applies when merchants are dissatisfied with the initial chargeback result or when issuing banks do not accept merchant evidence. Both parties can submit additional evidence, and the issuing bank evaluates it to decide whether to reverse the chargeback. If no agreement is reached, the dispute proceeds to formal arbitration. ### Reconciliation Service - [SFTP Service Application](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/reconciliation/transactionStatementDownload/index.md): SFTP reconciliation service is used to download transaction reports, all reports will be uploaded to the SFTP server in zip format. Before applying, you need to submit merchant server IP, RSA public key and ClientId to the designated email. - [Settlement Cycle and Reconciliation Statement](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/reconciliation/settlementCycle/index.md): The settlement cycle and reconciliation statement define the settlement rules and reconciliation methods for PingPongCheckout. Supports three settlement modes: T+(N), specified date, and weekly settlement, with specific cycles determined by contract. Reconciliation statements are generated daily, weekly, or monthly according to the settlement cycle, with data intervals corresponding to different settlement types to ensure accurate reflection of transaction status. - [Settlement File Path Rules on SFTP](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/reconciliation/settlementFilePath/index.md): The settlement file path rules on SFTP are used to guide merchants in finding billing files on the SFTP server. Each merchant's billing files are stored in directories named after `clientId\loginName`, with new subdirectories generated daily, weekly, and monthly in formats of `YYYYMMDD`, `YYYYMMDD-YYYYMMDD`, and `YYYYMM` respectively to store compressed files for corresponding periods. - [Settlement File Sheet Description](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/reconciliation/settlementFileSheet/index.md): The settlement file sheet description document introduces the billing template of PingPongCheckout and the purpose of each sheet, including key data such as settlement reports, transaction records, refunds, chargeback fees, etc., to help merchants perform financial verification and management. ### Integration Preparation - [Prerequisites](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/start/step/index.md): Prerequisites documentation introduces the necessary steps before using PingPongCheckout, including obtaining sandbox accounts, determining integration solutions, API authorization configuration, and production environment verification. It covers the entire process from testing to official launch, suitable for developers who wish to integrate payment solutions. - [Sandbox Access Instructions](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/start/registerSandbox/index.md): The sandbox access instructions provide steps to enter the PingPong payment system test environment. Suitable for developers to perform functional testing and integration debugging before official launch. The process includes registering an account through the designated website, selecting merchant type and submitting information, and obtaining necessary test parameters such as accId, clientId, and salt. After completing all preparations, contact technical support to configure the environment. - [Sandbox Constraint Limitations](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/start/limitSandbox/index.md): The sandbox environment provides developers with a secure, low-threshold testing platform that supports most core workflows and integration logic. However, please note that the sandbox is not 100% identical to the production environment, with functional limitations such as some payment methods unable to be fully tested or only able to simulate success states. Additionally, sandbox and production environment data are isolated, do not mix usage. - [Acceptance Test Scenarios](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/start/acceptance/index.md): The acceptance test scenarios documentation details key considerations for merchant acceptance, including sandbox environment characteristics, idempotency handling requirements, and credit card 3D verification testing methods. Suitable for the final testing phase before going live, ensuring payment processes are secure and reliable. ### Development Guide - [Basic Rules for API Usage](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/guide/APIUsage/index.md): The basic rules for API usage introduce the usage specifications of PingPongCheckout payment API V4, suitable for developers who need to integrate payment functionality. All requests must be sent via HTTPS and use JSON format. Key features include: support for UTF-8 character set, good parameter compatibility, and inclusion of necessary public request and response parameters such as accId, clientId, etc., ensuring security and data integrity - [API Endpoint Addresses](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/guide/endpoint/index.md): API endpoint address documentation introduces the online, terminal, and merchant backend API access domains provided by PingPongCheckout. Choose the corresponding site (FRA, SG, US) based on business scenarios and registration location, supporting sandbox and production environments, providing detailed API domain configuration and JS-SDK integration instructions. - [Signature Convention](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/guide/sign/index.md): The signature convention defines the request signature generation and verification rules for PingPongCheckout API v4 to ensure data security. Applicable to all scenarios using this API for payment processing. Supports both MD5 and SHA256 signature algorithms, with the more secure SHA256 recommended. Details the assembly of the string to be signed, signature value calculation steps, and provides example code for signature utility classes. - [Payment Notification Integration Guide](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/guide/paymentNotify/index.md): The payment notification integration guide introduces how to configure and receive asynchronous notifications from PingPongCheckOut. Developers need to provide a web service that supports HTTP POST, set an effective `notificationUrl` to receive JSON formatted notification data, and return HTTP status codes according to the agreement. The document also provides key details such as IP information for callback notification servers and retry mechanisms. - [LLM Documentation Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/guide/llms-integration/index.md): This document explains how to enable AI tools (Cursor, Windsurf, Claude) to automatically fetch PingPongCheckout API documentation through the llms.txt protocol for intelligent code completion and API call assistance. - [Payment Callback and Order Status Inquiry Implementation Guide](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/guide/bestPractices/fetchStatus/index.md): The payment callback and order status inquiry implementation guide introduces two methods for synchronizing transaction status in PingPongCheckout V4: asynchronous notifications and transaction queries. To ensure accurate order status updates, merchants are advised to redirect users to the payment result page via frontend redirection and call the order inquiry API to confirm status, while the backend should effectively handle asynchronous notifications and proactively initiate transaction queries when notifications are not received. Additionally, for orders that remain unpaid for extended periods, the system will automatically close the order and notify through designated channels. - [Currency Exchange Guide](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/guide/bestPractices/currencyExchange/index.md): The Currency Exchange Guide introduces the specifications for handling transactions in different currencies in PingPongCheckout. When the displayed currency differs from the actual payment currency, a currency exchange operation is required. The document provides currency exchange request parameter examples, credit card and APM display examples, and explains key parameters in asynchronous notifications such as `currency` and `exchangedCurrency`. Developers are reminded that exchange rate fluctuations may cause amount discrepancies. - [Transaction Idempotency](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/guide/paystatus/index.md): Introduces transaction idempotency patterns and status management. Supports two idempotency modes: non-failure final state and failure final state, covering different transaction states for automatic Capture and manual Capture. The document details state transition rules during the order lifecycle, including asynchronous notification mechanisms and order closure handling. Additionally, it emphasizes the global uniqueness requirement of merchantTransactionId and the use of retry windows. - [Transaction Recovery](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/guide/bestPractices/rescue/index.md): Transaction recovery guide introduces how to handle failed transactions due to reasons such as insufficient account funds. PingPongCheckout provides automatic retries or short-term retry windows for rejected payments that have a chance of success, to improve payment success rates. Merchants can avoid duplicate payments by setting the same requestId (Non-Hosted mode only). For transactions outside the retry window, it is recommended to add a suffix to the order number - [APM Integration Practice](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/guide/bestPractices/apmDemo/index.md): Introduces best practices for APM integration methods, suitable for developers who need to integrate local payment methods such as Klarna. The content covers methods for simulating payment effects, emphasizing that checkout page product information is independent from actual payment request parameters, facilitating flexible testing and development. - [Special Payment Methods Refund Instructions](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/guide/bestPractices/specialRefund/index.md): Special payment methods refund instructions introduce how to perform refund operations for specific payment methods, including VNM QR, promptPay and VA, etc. Each payment method's refund request must follow specific parameter requirements such as account number, mobile phone number or email address, and some parameters are mandatory. Please confirm with technical support before integration. ### Risk Management - [Dynamic 3D Secure](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/risk/3ds/index.md): Dynamic 3D Secure is a security protocol used for online transaction verification and fraud prevention. It applies to websites or mobile applications that support PingPongCheckout, adding an additional security layer during the payment process. The system automatically determines whether to enable 3D authentication based on risk assessment. The authentication process includes two methods: Frictionless, which requires no user interaction, and Challenge, which requires additional verification. - [Overview](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/risk/overview/index.md): Overview of 'Disputes' and 'Chargebacks' concepts and processing workflows in payments and banking. Suitable for merchants to understand how to handle transaction disputes initiated by customers, including retrieval requests, chargeback notifications, pre-arbitration, and formal arbitration processes. The Rapid Dispute Resolution (RDR) mechanism is also introduced, designed to simplify dispute resolution through automation. - [Overview](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/risk/disputesAPI/index.md): dispute API Used for automated processing of payment disputes, supporting proactive retrieval of transaction information and chargeback details, querying and uploading defense materials, and other functions. Suitable for rapid response and management of the entire process after dispute initiation, including submitting or abandoning appeals. Through this API, merchants can more efficiently handle issuer's retrieval requests and chargeback situations. - [Dispute Notification Integration Guide](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/risk/disputeNotify/index.md): The dispute notification integration guide provides merchants with instructions on how to receive and process dispute-related events. Suitable for merchants who need real-time awareness and response to dispute situations, by configuring the callback address provided by technical support to receive JSON format asynchronous notifications sent by PingPongCheckOut via HTTP POST. Key features include support for specific eventCode to identify dispute stages, and returning HTTP 200 ### Quick Start - [Sandbox Environment Usage Guide](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/onlinePayment/sandbox/index.md): The sandbox environment is provided for developers to perform interface development and debugging, with accounts limited to use within this environment. Access address is https://sandbox-acquirer-payment.pingpongx.com. Multiple test accounts and supported local payment methods are provided, including Wechat Pay, AlipayCN, etc., along with card numbers available for testing and their properties such as whether 3DS is supported - [Klarna Test Resources](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/onlinePayment/Klarna/index.md): Klarna test resources provide test accounts and payment material information for online payment integration, supporting payment simulation in regions such as the United States, Finland, Germany, and Austria. Key features include strict validation of billing and shipping address information, as well as special configuration requirements when accessing virtual industries. - [Capture](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/onlinePayment/modify/Capture/index.md): Capture function is used for payment methods that support separate capture such as international credit card payments, divided into two steps: authorization and capture. Supports automatic and manual capture strategies, default is automatic capture. Manual capture requires setting captureDelayHours parameter and calling CAPTURE-Pre-authorization Confirmation API. Key parameters include merchantTransactionId, merchantCapture - [VOID](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/onlinePayment/modify/Void/index.md): VOID operation is used to cancel an authorized but uncaptured payment, releasing reserved funds. Applicable to payment methods that support separate Capture such as international credit card payments. Initiate and receive asynchronous notifications by calling the VOID-Pre-Authorization Cancellation API and setting notificationUrl. Status includes SUCCESS, FAILED, and PROCESSING. Multiple calls require different merchant IDs. - [Refund](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/onlinePayment/modify/Refund/index.md): The refund function allows merchants to return partial or full amounts to shoppers after a transaction is completed. Applicable to captured payments, supports full and multiple partial refunds. Initiate refunds by calling the apply refund API, set notificationUrl to handle refund status. Refunds have time limits and are idempotent based on merchantRefundId, ensuring safe multiple calls. - [Tokenization](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/onlinePayment/features/tokenization/overview/index.md): Tokenization technology is used to securely store shoppers' payment information, supporting major card brands and some local payment methods. By generating tokens, faster checkout, subscription payments, auto-recharge and other functions can be achieved. Payment information is collected and a token is generated during the first payment, and subsequent payments can use this token. Tokens are stored by merchant accId by default. If not fully compliant with PCI DSS requirements, it is recommended to use Tokenization - [NetworkToken](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/onlinePayment/features/tokenization/networkToken/index.md): NetworkToken is a feature in the online payment module that enables secure payments through card scheme tokens. It is suitable for scenarios that require improved transaction security and efficiency. Key parameters include paymentMethod.type (fixed as networkToken), schemeTokenValue (card scheme token), paymentBrand (card brand, supports - [CardOnFile](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/onlinePayment/features/tokenization/cardOnFile/index.md): The CardOnFile feature supports merchants to store and reuse user's payment card information after user authorization. Key parameters include bizType, merchantUserId, createToken and token, used to identify transaction type, user identity and card information flag. By creating card token, verifying card elements (optional), displaying card list (optional) and using card token - [CodeGrant](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/onlinePayment/features/tokenization/codeGrant/index.md): CodeGrant is an authorized payment method in the PingPongCheckout online payment module, suitable for scenarios where users need to sign up before making payments. Obtain the authUrl through the binding interface to complete user sign-up, then use the order and payment interface to pass in the token, bizType (fixed as 'CodeGrant'), and merchantUserId to complete the payment. Supports unbinding functionality. - [Overview](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/onlinePayment/recurring/overview/index.md): Subscription payment service allows merchants to automatically deduct funds from user authorized accounts according to preset cycles, suitable for membership services, regular product consumption and other scenarios. Cardholders need to first authorize the subscription plan and payment information, after which the system will automatically execute deductions based on established rules. Subsequent deductions can only take effect after the initial payment is successful. Please confirm deduction and retry policies with technical support before use. - [Recurring Payment](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/onlinePayment/recurring/recurring/index.md): The Recurring Payment API allows merchants to implement regular automatic deduction functions, suitable for services that require periodic charging. Supports both Hosted and Non-Hosted integration modes. The main process includes cardholder authorization and scheduled deductions. Key parameters include bizType (fixed value Recurring) and primaryMerchantTransactionId (first transaction identifier). ### Integration Methods - [Overview](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/overview/index.md): Introduction to selecting and configuring integration methods for online payment products. Covers multiple solutions from pre-built integrations to custom checkout experiences, suitable for merchants with different technical levels and requirements. Recommended integration methods include redirect checkout, embedded SDK, and S2S, which are respectively suitable for low technical investment, light customization, and fully custom scenarios. Additionally, provides no-code integration options such as Payment Link, as well as compatibility support with various platforms and plugins. - [SaaS Website Building Platform](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/sass/index.md): Introduces how to integrate PingPongCheckout payments on mainstream SaaS website building platforms, suitable for merchants who want to quickly access payment solutions without additional development. With simple configuration, supports platforms like Shopify, Magento, etc., covering major global markets and providing secure and convenient payment experiences. - [Plugins](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/plugin/index.md): The plugin module introduces a series of integration solutions designed for open-source e-commerce platforms, aimed at optimizing the checkout process. These plugins support PingPongCheckout payment functionality, are easy to install and simply configured, suitable for merchants looking to enhance customer payment experiences. - [Pay by Link](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/payByLink/index.md): Pay by Link is a quick payment solution provided by PingPong for merchants, suitable for scenarios that do not require website integration. By adding payment information in the PingPongCheckout backend, a link is generated and sent to the user's email. Users click the link to enter the payment page and complete the transaction. It supports global payments with main features including simple operation and fast integration. Contact operations to enable permissions before use. - [Overview](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/hosted/index.md): This document introduces payment integration methods and configurations, including re-payment, card saving features, and embedded SDK characteristics. It is suitable for optimizing user payment experience, supporting re-payment of orders that failed to pay within 48 hours, and providing card saving to simplify the next payment process. The embedded SDK is based on Web Component technology and ES2021 standards, lightweight and fast, compatible with modern mainstream browsers, customizable skin, and payment settings - [Embedded SDK (Pre-order)](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/sdk-v4/index.md): Embedded SDK (Pre-order) provides a method to quickly integrate payment functionality through JavaScript-SDK, suitable for scenarios that require directly embedding payment interface in web pages. Supports sandbox and multiple production environment deployments, allows custom payment buttons and language settings, and provides hook functions such as beforeCheckoutHook and checkoutFailedHook to meet specific business needs. - [OnePage Checkout](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/sdk-v4-2/index.md): This solution is specifically designed for merchants who have adopted the OnePage Checkout model, providing embeddable payment components that seamlessly integrate into your existing checkout page. Without changing the original checkout flow, you can quickly access PingPong payment capabilities, supporting multiple mainstream payment methods covering regions such as Europe and Singapore. - [PingPong Element SDK Integration Guide](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/sdk-elements/index.md): PingPong Element SDK supports diverse payment scenarios such as order placement and payment, wallet binding. Adopting a new architecture design, it provides unified API interfaces, flexible event models, and extensible payment components. The integration process includes importing SDK scripts, initialization configuration, creating payment elements, event listening and handling, and provides marketing campaign integration functionality. - [Native SDK](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/native-sdk/index.md): PingPong Checkout Native SDK is a native checkout SDK for mobile applications, providing a bottom-sheet payment experience. Supports iOS and Android platforms with credit/debit card payments, Apple Pay, Google Pay, and more. - [Native SDK - iOS Integration Guide](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/native-sdk-ios/index.md): Complete guide for integrating PingPong Checkout Native SDK on iOS, covering environment requirements, import instructions, SDK configuration, key integration steps, and Apple Pay configuration. - [Native SDK - Android Integration Guide](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/native-sdk-android/index.md): Complete guide for integrating PingPong Checkout Native SDK on Android, covering environment requirements, import instructions, SDK configuration, and key integration steps. - [Compliance Overview](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/native-sdk-compliance/overview/index.md): PPCashDeskSDK Native SDK compliance guide. Describes the SDK's impact on store compliance and the actions merchants need to take. - [iOS App Store Compliance](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/native-sdk-compliance/appstore/index.md): PPCashDeskSDK compliance impact on iOS App Store submission, including Privacy Manifest requirements and merchant actions. - [Android Google Play Compliance](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/native-sdk-compliance/google-play/index.md): PPCashDeskSDK compliance impact on Android Google Play submission, including Data Safety declaration and permission requirements. - [Redirect to Checkout](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/link/index.md): Redirect to Checkout is a payment integration method that completes payment by redirecting to the checkout page after obtaining the paymentUrl from the order response. Supports multi-language settings, defaulting to English; if other languages are specified, the passed values will be used. Suitable for scenarios requiring quick payment function integration, ensuring users can smoothly complete the payment process in a familiar language environment. - [Non-hosted International Credit Card Payment](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/non-hosted-card/index.md): Non-hosted international credit card payment solution is suitable for merchants with PCI-DSS certification who can develop and process cardholder information independently. This solution collects risk control parameters through SafePayGuardJs and SecureShieldJs plugins, and submits them to PingPongCheckout server for processing after the user clicks payment. Supports credit card payments worldwide and provides 3D security - [Non-hosted Local Payment](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/non-hosted-apm/index.md): Non-hosted local payment provides a payment integration solution that does not require redirection to third-party pages, suitable for merchants who want to complete transaction processes on their own platform. It mainly creates orders by calling the order creation and payment API, and decides whether to display QR codes or redirect links based on parameters in the returned action object to guide users to complete payments. Supports asynchronous notification mechanism to ensure transaction status synchronization, covering extensive regions including but not limited to Asia ### Checkout - [Payment Order Interface (Hosted Mode)](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/checkout/api/reserve/index.md): The payment order interface is used to create payment orders in Hosted mode. It is suitable for scenarios that require hosting the payment process with a payment service provider. Key features include uniquely identifying a transaction through merchantTransactionId, where parameters corresponding to this ID cannot be changed once created; if parameter modifications are needed, a new merchantTransactionId must be used to re-initiate the request. - [Direct API (Non-Hosted Mode)](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/checkout/api/uniformly/index.md): Direct API (Non-Hosted Mode) is used to implement order creation and payment functions in the checkout module. Suitable for scenarios that require direct integration of payment processes, supporting multiple payment methods. When using this mode, please note that card payments in non-hosted mode must integrate risk control components to ensure transaction security. Main parameters include order information and payment method configuration. - [capture](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/checkout/api/modifications/capture/index.md): The pre-authorization confirmation API is used by merchants to complete the final transaction amount deduction after obtaining customer payment card information. It applies to scenarios such as online shopping and hotel reservations that require fund freezing before actual payment. Key functions include executing deduction operations based on pre-authorization ID and supporting adjustment of deduction amounts. Main parameters include pre-authorization ID, deduction amount, and currency type. - [VOID - Pre-Authorization Cancellation](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/checkout/api/modifications/void/index.md): The pre-authorization cancellation API is used to cancel pre-authorization transactions that have been executed but not yet completed settlement. It applies to situations requiring immediate stoppage of pre-authorized charges, such as order cancellation or payment method changes. Key functions include canceling specified pre-authorizations and providing real-time cancellation status feedback. Key parameters include the pre-authorization ID and merchant order number. - [Request Refund](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/checkout/api/modifications/refund/index.md): The refund request interface is used to handle user refund requests after payment. It applies to scenarios requiring refund operations and supports both instant and delayed refunds. Main functions include submitting refund applications, querying refund status, etc. Key parameters include order number, refund amount, and refund reason. - [close](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/checkout/api/modifications/close/index.md): The close payment session API is used to end the current payment process. It is suitable for scenarios that require terminating incomplete payment operations, such as user order cancellation or payment timeout. Main functions include sending close requests and receiving confirmation responses. Key parameters include session_id and merchant_order_no. - [LogisticsUpload](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/checkout/api/LogisticsUpload/index.md): The LogisticsUpload API is used to upload order logistics information. It is suitable for scenarios where merchants need to update order logistics status after users complete payment on e-commerce platforms. Key features include adding or updating logistics details, with main parameters including order ID, logistics company, and tracking number. - [Transaction Query](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/checkout/api/getOne/index.md): The transaction query API is used to retrieve detailed information about a specific transaction. It applies to scenarios that require status tracking and management of completed or ongoing transactions. Main functions include obtaining transaction details through transaction ID, with the key parameter being transaction_id. - [getVoid](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/checkout/api/getVoid/index.md): getVoid API is used to query the pre-authorization void status. Applicable to scenarios where the void result needs to be confirmed after completing the pre-authorization transaction, ensuring it is called after the synchronous return to avoid query exceptions. Main functions include verifying whether the void was successful and returning relevant status information. - [getCapture](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/checkout/api/getCapture/index.md): The pre-authorization confirmation query API is used to obtain the confirmation status of payment pre-authorization. It is suitable for scenarios that need to verify whether the pre-authorization was successful, supporting payment methods worldwide. When calling, attention should be paid to performing it after synchronous return to avoid query exceptions. Request responses use JSON format, containing key parameters such as transaction ID, ensuring accurate tracking of each transaction's status. - [getRefund](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/checkout/api/getRefund/index.md): getRefund The interface is used to query the status of initiated refund requests. It is suitable for scenarios that need to confirm whether the refund was successful. Please ensure the refund synchronous return is completed before calling to avoid query exceptions. Main functions include obtaining refund details through order number or refund number, with key parameters order_id and refund_id. - [Get sdkAccessToken](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/checkout/api/getAccessToken/index.md): Obtain sdkAccessToken to verify merchant identity during the checkout process. Suitable for online stores or applications that need to integrate payment functionality, supporting global payment processing. Main features include generating temporary access tokens, with key parameters such as merchantId and apiKey, ensuring a secure and reliable payment experience. ### Async Notification - [Payment Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/payment/notify/index.md): The payment notification interface is used to receive payment status updates. Suitable for merchants who need real-time awareness of payment results, supporting notifications for order payment success, failure, and other status changes. This interface sends HTTP POST requests asynchronously to the merchant's specified URL, with key parameters including transaction number, order amount, and payment status. - [Refund Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/refundNotify/index.md): The refund notification interface is used to receive refund results sent by the payment platform. It is suitable for scenarios where merchants need real-time awareness of refund status, supporting automatic processing of refund information. Key parameters include refund order number, refund amount, and refund status. - [Order Closure Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/closeNotify/index.md): The order closure notification interface is used to send asynchronous notifications to merchants when an order is automatically or manually closed by the system. It is suitable for scenarios that require real-time awareness of order status changes. Key features include support for multiple closure reason identifiers and provision of detailed order information, ensuring that merchants can respond promptly and handle related business logic. - [Pre-Authorization Capture Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/status/captureNotify/index.md): The pre-authorization capture notification interface is used to receive pre-authorization capture results sent by the payment platform. It is suitable for scenarios that require verification of the final status of pre-authorization transactions, such as hotel reservations or car rental services. Main functions include real-time transaction status updates, with key parameters including order number, transaction amount, and capture status. - [Pre-Authorization Void Asynchronous Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/status/voidNotify/index.md): Pre-authorization void asynchronous notification is used to receive and process the results of pre-authorization voids. Suitable for merchant systems that need real-time awareness of pre-authorization void status. This notification is sent asynchronously to ensure high reliability and low latency. Key parameters include transaction number, merchant order number, and void result, helping merchants update order status in a timely manner. - [Notification of Predispute](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/dispute/apis/eventCode/predispute/index.md): Notification of Predispute interface is used to receive dispute event notifications that have not been escalated to formal disputes. Suitable for early warning and preventive processing scenarios, helping merchants take action before disputes escalate. Key features include providing dispute warning information, reason explanations, and recommended measures. Main functions include receiving asynchronous notifications, key parameters include event code, merchant order number, and dispute details. - [Information Request Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/dispute/apis/eventCode/information/index.md): The information request notification API is used to receive asynchronous notifications of payment dispute events. It applies to payment dispute scenarios such as refunds and chargebacks, ensuring merchants can respond and handle related issues promptly. Key features include automatically sending information requests to the specified URL, supporting multiple event types such as refund requests and chargeback notifications. Main parameters include event code, order ID, and transaction details. - [Fraud Alert Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/dispute/apis/eventCode/fraud/index.md): The fraud alert notification API is used to send real-time notifications to merchants when potential fraudulent activities are detected. It is suitable for online payment scenarios that require immediate response to fraud activities, supporting transaction monitoring worldwide. Key features include providing detailed transaction information, fraud scores, and recommended measures. Main functions cover receiving asynchronous notifications, with key parameters including event code (eventCode), merchant order number, and fraud details. - [Chargeback Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/dispute/apis/eventCode/chargeback/index.md): The chargeback notification interface is used to receive and process payment status change information caused by customer chargebacks. It applies to all merchants who need real-time transaction monitoring and timely response to chargeback situations. Key features include support for multiple payment methods, automatic order status updates, and detailed chargeback reason descriptions. Main parameters cover event code, order ID, and chargeback details. - [Pre-Arbitration Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/dispute/apis/eventCode/prearbitration/index.md): The pre-arbitration notification interface is used to send notifications to merchants when a payment dispute enters the pre-arbitration stage. It is applicable for handling payment dispute scenarios and supports payment services worldwide. This API allows merchants to timely understand and respond to potential financial risks. Key parameters include event code, transaction ID, and amount information, ensuring merchants can accurately identify and process related cases. - [Dispute Reversal Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/dispute/apis/eventCode/reversed/index.md): The dispute reversal notification API is used to receive and process events where banks or payment institutions cancel disputes after users initiate them. Suitable for merchant systems requiring real-time transaction status updates, supporting global payment channels. Key parameters include event code, transaction ID, and reversal time, ensuring merchants can promptly adjust their accounting processing strategies. - [Pre-arbitration Won Result Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/dispute/apis/eventCode/prearbitrationWon/index.md): The pre-arbitration won result notification API is used to receive notifications of successful outcomes in payment dispute handling. Suitable for merchants who need to understand and record the final results of disputes. This API sends notifications asynchronously, ensuring secure and real-time data transmission. Key parameters include event code, transaction number, and processing results, supporting payment dispute handling globally. - [Pre-arbitration Lost Result Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/dispute/apis/eventCode/prearbitrationLost/index.md): The pre-arbitration lost result notification API is used to receive and process notifications of pre-arbitration failures in transaction disputes. Suitable for scenarios where merchants need to respond promptly to dispute ruling results, supporting payment dispute handling worldwide. Key parameters include event code, merchant ID, and dispute details, ensuring merchants can quickly take corresponding measures to protect their rights and interests. - [Dispute Defense Period Ended Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/dispute/apis/eventCode/disputeDefensePeriodEnded/index.md): The Dispute Defense Period Ended notification API is used to inform merchants that the dispute defense period has ended. It applies to payment dispute processing, ensuring merchants are promptly aware of the dispute process status. Key parameters include event code (eventCode), transaction ID (transactionId), etc., helping merchants update internal records and take appropriate actions. - [Arbitration Stage Entry Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/dispute/apis/eventCode/arbitiration/index.md): The Arbitration Stage Entry Notification API is used to send asynchronous notifications to merchants when a payment dispute escalates to the arbitration stage. It is suitable for handling transaction situations involving complex disputes and supports global payment platforms. Key parameters include event code, order number, and arbitration details, helping merchants respond promptly and manage transactions in arbitration status. - [Contract Success Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/bindNotify/cof/accTokenCreation/index.md): The contract success notification interface is used to send asynchronous notifications to the merchant system after the user completes payment account binding. It is suitable for scenarios that require real-time awareness of user payment account binding status, and supports payment service access worldwide. Key features include passing data through HTTPS POST method to ensure information transmission security; the message body contains important parameters such as contract results and user identification, facilitating subsequent processing by merchants. - [Merchant Unbinding Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/bindNotify/cof/accTokenCancelMerchant/index.md): The merchant unbinding notification interface is used to receive asynchronous notifications when merchants cancel their bindings. It is suitable for scenarios that require real-time awareness of merchant binding status changes, supporting key features including instant notification through callback URL, providing important information such as merchant ID and cancellation reasons, ensuring the platform can respond and handle related business changes in a timely manner. - [Contract Success Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/bindNotify/APM/accTokenCreation/index.md): The contract success notification interface is used to send asynchronous notifications to the merchant system after the user completes the payment contract. It is suitable for scenarios that require real-time awareness of user contract status. This interface is called via POST method, and the returned key parameters include contract ID, merchant ID, and contract status information. - [Merchant Unbinding Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/bindNotify/APM/accTokenCancelMerchant/index.md): The merchant unbinding notification interface is used to receive notifications when merchants cancel their payment service binding. It is suitable for scenarios that require real-time awareness of merchant status changes, supporting asynchronous notification reception. Key parameters include merchantId (merchant ID) and cancelTime (cancellation time). - [User Cancellation of Subscription Notification from Wallet Side](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/bindNotify/APM/accTokenCancelMerchantUser/index.md): The user cancellation of subscription notification interface from wallet side is used to receive notifications when users cancel their subscription status with merchants. It is suitable for scenarios that require real-time updates of user subscription status, ensuring system data consistency. This interface sends notifications asynchronously, including key parameters such as user identifier and merchant number. ### Dispute - [Actively Retrieve Retrieval Details](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/dispute/v4-apis/getRetrievalDispute/index.md): The Actively Retrieve Retrieval Details API is used to query detailed information of specific chargeback cases. It is suitable for scenarios that require detailed understanding of chargeback reasons and processing status. The main function includes obtaining detailed retrieval data by specifying the case ID, with key parameters such as disputeId. - [Proactively Retrieve Chargeback/Dispute Details](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/dispute/v4-apis/getDisputeInfo/index.md): The Proactively Retrieve Chargeback/Dispute Details API is used to query detailed information about specific chargeback or dispute cases. It is suitable for merchants who need to understand the reasons, status, and handling recommendations of chargebacks or disputes. Main functions include obtaining relevant information through a specified case ID, with key supported parameters including dispute_id. - [Query Dispute Defense Materials](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/dispute/v4-apis/getDefenseReasons/index.md): The Query Dispute Defense Materials API is used to obtain defense reasons and related information required for handling disputes. It is applicable when merchants need to prepare corresponding defense materials to争取 fund returns after receiving dispute requests initiated by consumers through banks. Main functions include listing all available defense reasons and their corresponding status codes, with key parameters being dispute_id and reason_code. - [Upload File](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/dispute/v4-apis/disputeUploadFile/index.md): The upload file API is used to submit relevant evidence files to the system during the dispute resolution process. It is applicable for situations where supporting materials need to be provided for specific transactions or service disputes, supporting multiple file type uploads. Key parameters include file path, file type, and association identifier with specific dispute cases. - [Upload Dispute Evidence](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/dispute/v4-apis/supplyDefenseDocument/index.md): The Upload Dispute Evidence API is used to submit defense documents from merchants regarding disputes. It is applicable when merchants encounter credit card transaction disputes and need to provide relevant evidence supporting their position to the payment platform through this interface. Key parameters include case ID, document type, and file content. - [Delete Dispute Evidence](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/dispute/v4-apis/deleteDefenseDocument/index.md): The delete dispute evidence API allows merchants to remove uploaded dispute-related files. It is suitable for scenarios that require updating or cleaning up existing evidence materials. By specifying dispute_id and document_id as key parameters, the target file can be accurately located and deleted. This feature helps maintain the accuracy and timeliness of information during the dispute handling process. - [Submit Materials and Defend Dispute](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/dispute/v4-apis/defendDispute/index.md): The Submit Materials and Defend Dispute API allows merchants to dispute chargebacks. It applies when merchants receive chargebacks initiated by customers through banks and need to provide evidence supporting the legitimacy of their transactions. Key features include uploading supporting documents, filling in dispute reasons, etc. Main parameters include disputeId, evidenceType, and evidenceContent. - [Accept Dispute](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/dispute/v4-apis/acceptDispute/index.md): The Accept Dispute API is used when merchants decide not to dispute a specific chargeback. This is applicable when merchants assess that continuing the dispute is not beneficial or when they wish to quickly resolve the chargeback situation. Through this API, the current dispute process can be terminated, requiring the transaction identifier as a key parameter. ### Tokenization - [Card Binding to Obtain Credentials](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/tokenization/cof/bind/index.md): The card binding to obtain credentials feature supports users in securely storing payment information, suitable for scenarios requiring simplified payment processes and improved payment experiences. By converting users' bank card information into irreversible tokens, it ensures the security of sensitive data. This feature covers major global markets, supports multiple bank card types, and provides API interfaces for easy integration, with key parameters including customer ID, card information, etc. - [Card Binding Query API](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/tokenization/cof/bindList/index.md): The card binding query API provides retrieval services for bound bank card information. It is suitable for application scenarios that need to obtain details of user-bound payment methods, supporting queries for all valid cards under a customer ID. The returned data includes but is not limited to card aliases, types, and partially masked card numbers, facilitating further processing or display to users. - [Unbind API](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/tokenization/cof/unbind/index.md): The unbind API is used to cancel the association between a bound payment card and user account. It applies to scenarios that require removing or updating payment methods, supporting payment card operations worldwide. By calling this API, developers can securely and efficiently manage users' payment card information. Key parameters include user identifier and the token of the card to be unbound. - [Binding Interface](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/tokenization/oneClickPayment/bind/index.md): The binding interface is used to tokenize and store user's bank card information, supporting subsequent quick payments. It is suitable for scenarios such as e-commerce platforms and mobile applications, improving payment security and convenience. Main functions include generating and managing card tokens, with key parameters including merchant ID, user ID, and card information. - [Contract Inquiry Interface](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/tokenization/oneClickPayment/bindList/index.md): The contract inquiry interface is used to retrieve the list of payment cards already bound by the user. It is suitable for application scenarios that need to display or manage user payment methods, supporting major regions worldwide. Through this API, developers can implement one-click payment functionality to enhance user experience. Requests must include necessary authentication information, and the response contains key parameters such as card type and partially masked card number. - [Unbind Interface](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/tokenization/oneClickPayment/unbind/index.md): The unbind interface is used to解除已绑定的支付卡, applicable when users no longer use a specific card for quick payments or need to change payment methods. This interface belongs to the tokenization module, and by providing necessary parameters such as token_id, it can securely cancel the association between the card and account, ensuring user information security while simplifying the management process. ### Partner Platforms - [Shopify](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/saas/Shopify/overview/index.md): Shopify x PingPong Checkout integration guide, providing three integration methods: card embedded, local payment aggregated checkout, and local payment tiled display. Supports multiple local payment methods such as Sofort, Trustly, iDEAL, MyBank, Multibanco, Blik, Afterpay, Klarna and more displayed directly on the page, allowing consumers to clearly understand the payment options supported by the merchant. - [Shopify x PingPong Checkout Credit Card Embedded Installation Guide (International Cards)](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/saas/Shopify/card/index.md): Shopify x PingPong Checkout international card embedded installation guide, suitable for merchants who wish to integrate PingPong payment solutions in their Shopify stores. This guide covers the entire process from searching and installing the APP to completing testing and closing the original checkout, ensuring merchants can smoothly access international credit card payment functions and support global transaction processing. - [Local Payment - Unified Checkout](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/saas/Shopify/apm/index.md): Local payment unified checkout installation guide, suitable for merchants on Shopify platform to integrate local payment methods. By searching and installing the PingPong Local Payment APP, merchants can add local payment options to their stores, covering extensive regions and supporting multiple local payment methods. After successful installation, provide a product link for PingPong team testing to ensure smooth payment flow before official use. - [Custom Checkout](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/saas/Shopify/checkoutCustomize/index.md): The custom checkout feature is suitable for e-commerce and virtual merchants, especially small and medium-sized merchants with brand style requirements. By unifying the interaction style of product browsing, ordering, and payment processes, it significantly enhances user experience and improves conversion rates. Supports different styles for different websites, including colors, styles, and font sizes. Not supported for merchants who have already used API or customized checkout styles. - [Shopify Logistics Binding](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/saas/Shopify/Logistics/index.md): The Shopify logistics binding documentation guides users on how to install and configure logistics applications on the Shopify platform to automatically capture shipping information for orders. This process includes creating a custom App, configuring permissions, saving tokens and store subdomain names, and completing the final binding in the PingPong Checkout backend. Ensuring timely upload of logistics information helps meet compliance requirements and avoids affecting withdrawal review and settlement limits. - [Sofort](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/saas/Shopify/sofort/index.md): Sofort is an online payment method suitable for European regions, primarily supporting Euro transactions. After installing this app through a Shopify store, merchants can find this option in the Payments section of their backend and provide customers with this convenient payment method at checkout. Currency must be set to EUR before installation. - [Trustly](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/saas/Shopify/Trustly/index.md): Trustly is an online banking transfer service that supports Euro payments. Suitable for Shopify merchants, providing a secure and convenient payment solution. Installation steps include checking store currency settings to EUR, searching and installing the Trustly app through the specified link. After successful installation, the app can be found in the Payments section of the Shopify backend, and this payment option will be displayed at checkout. - [iDEAL](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/saas/Shopify/ideal/index.md): iDEAL is a local Dutch payment method for the Shopify platform, supporting Euro transactions. After installation via the specified path, merchants can enable this payment option in the backend Payments section and offer it to consumers at checkout. Main steps include confirming store currency as EUR, searching and installing the corresponding APP, after which the new payment method can be displayed on the frontend. - [MyBank](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/saas/Shopify/Mybank/index.md): MyBank is a European local payment method for the Shopify platform, supporting Euro transactions. After installation through the specified path, merchants can enable this payment option in the backend Payments section and provide it to consumers at checkout. Main steps include confirming store currency as EUR, searching and installing the corresponding APP, after which the new payment method can be displayed on the frontend. - [Multibanco](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/saas/Shopify/Multibanco/index.md): Multibanco is a Portuguese local payment method for the Shopify platform, supporting Euro transactions. Installation steps include checking if the store currency is EUR, searching and installing the corresponding APP in the Shopify App Store. After successful installation, this payment method will appear in the merchant backend Payments option and checkout. - [Blik](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/saas/Shopify/Blik/index.md): Blik is a payment method designed specifically for the Polish region, supporting PLN currency. It is suitable for the Shopify platform, ensuring that the store currency is set to PLN and both shipping origin and destination are in Poland. After installing the corresponding APP, merchants can enable this payment option in the Payments section of the backend, while the payment method will be displayed at checkout. - [Afterpay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/saas/Shopify/Afterpay/index.md): Afterpay is an installment payment solution for the Shopify platform that supports USD settlement. Merchants need to first confirm that their store currency is USD, then install the Afterpay app through the specified link. After successful installation, this payment option will automatically appear in the Payments section of the Shopify backend and on the checkout page, making it convenient for consumers to choose. - [Klarna](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/saas/Shopify/Klarna/Klarna/index.md): Klarna is a payment method for the Shopify platform that supports multiple countries including Austria, Canada, Denmark, and their corresponding transaction currencies. By installing the Klarna PingPong app, merchants can provide flexible payment options in their Shopify stores. Installation steps include verifying that store currency matches the target country, installing Klarna P from the Shopify app store - [Installation and Configuration Guide for Klarna's OSM Plugin](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/saas/Shopify/Klarna/OSM/index.md): Installation and configuration guide for Klarna's OSM plugin, applicable to Shopify stores, helping merchants enhance customer payment experience through on-site messaging. The document details how to install the Klarna OSM App from the Shopify App Store and integrate the plugin in Shopify 2.0 themes, including adding Klarna OSM locations, accessing application blocks and configuring display positions. ### Marketplaces API ### Marketplaces ### InPersonPayments ### Terminal Integration API ### Recurring Payment - [Subscription Payments](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/recurring/recurring/index.md): Subscription payment API supports recurring automatic deduction functionality, suitable for scenarios that require long-term fee collection from users. Provides two integration modes: Hosted and Non-hosted. Key steps include cardholder authorization and scheduled deductions, by setting `bizType` to `Recurring` to mark the transaction type, and using the `primaryMerchantTransact ### Services - [Hosted](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/services/checkout/hosted/hosted/index.md): Hosted mode provides a solution for embedding PingPong Checkout cash register into merchant websites. Suitable for scenarios requiring quick integration of payment functions, it supports both JS-SDK initialization and redirect methods for rendering the cash register. The main process includes order submission, cash register initialization, buyer payment information filling and confirmation steps. Additionally, it provides 3DS verification options to enhance transaction security. ### 3D Secure - [3D Secure Authentication Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/threeDS/3ds/index.md): 3D Secure is an online transaction verification protocol designed to prevent fraud in e-commerce. By requiring cardholders to enter passwords or one-time codes, it provides additional security for the payment process. PingPongCheckout supports three 3ds decision schemes: enforcement, risk control decision, and external execution. The authentication process includes frictionless and challenge modes, where the former completes authentication without further user interaction, while the latter requires ### Payment Methods - [Virtual Account Korea](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/virtualAccountKorea/index.md): Virtual Account Payment is a commonly used online payment method in South Korea that allows users to complete payments through bank transfers. Key features include instant arrival notifications, support for multiple local Korean banks, and applicability to e-commerce platforms and various online service scenarios. This payment method provides a convenient and secure transaction experience, particularly suitable for businesses requiring frequent small payments. ### Coverage Regions - [Coverage Regions](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/Global/index.md): The coverage regions module introduces global payment methods supported by PingPongCheckout, enabling businesses to accept e-wallet and credit card payments from around the world through a single integration, expanding international business reach. - [Coverage Area](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/asiaPacific/JP/index.md): Coverage area documentation introduces Japan's unique payment market, where despite being the world's third largest economy, cash payments account for 82%. Convenience store payments (Konbini) account for 10% of total purchases, becoming the second most common payment method. Due to Japan's low cross-border shopping rate, localization strategy is crucial for entering this market. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/asiaPacific/southKorea/index.md): South Korea, as one of the world's leading e-commerce markets, is expected to see continued growth in retail e-commerce transaction volume. Credit card usage is extremely high in this region, with an average of 6.7 cards per person, accounting for 70% of all payment methods, including locally issued single-brand cards and dual-brand cards that partner with international payment systems. Additionally, online banking and e-wallets such as KakaoPay are also popular in e-commerce. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/asiaPacific/IN/index.md): Coverage area documentation introduces the rapid growth of India's internet and e-commerce market and its payment characteristics. India has 390 million internet users, with 160 million shopping online, showing huge market potential. Despite digital transformation facing challenges such as urban-rural differences and unequal internet access by gender, payment methods are diverse: bank cards are popular with over 900 million debit and credit cards; local and international payment systems coexist, including RuPay; emerging payment methods such as online banking - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/asiaPacific/ID/index.md): Describes the rapid development of e-commerce and mobile payments in Indonesia. The country has a young population of 271 million, with significant growth in the digital economy, especially in e-commerce and digital wallets. 60% of internet users access the internet through smartphones, and mobile wallets such as Dana, PayPal, and DOKU are rapidly gaining popularity. Despite only 50% of the population being online and card penetration being below 20%, the development potential is enormous. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/asiaPacific/TH/index.md): Introduces the characteristics of digital transformation in Thailand's payment market. Digital payments are growing rapidly, with government promotion of electronic payment systems and increased usage of mobile payments and e-wallets such as TrueMoney, Rabbit LINE Pay, and AirPay. QR code payments are popularized, with the PromptPay standard promoting digitization of small-value payments. Major banks have launched mobile banking applications providing comprehensive digital financial services including transfers, payments, and investments. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/asiaPacific/VN/index.md): Vietnam's payment market is experiencing high growth, with young demographics driving technology adoption. Cash and digital payments coexist, local companies dominate the market, and the government supports cashless policies. The market is highly competitive, with low financial service coverage in rural areas offering significant development potential. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/asiaPacific/PH/index.md): Covers the e-commerce and payment market characteristics of the Philippines. This region is one of the fastest-growing e-commerce markets in Southeast Asia, with a growth rate of 25% annually, primarily driven by high internet usage and mobile device penetration. Despite low credit card adoption, digital wallets such as GCash are rapidly developing, reaching 30 million users. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/asiaPacific/MY/index.md): Coverage area documentation introduces the characteristics of Malaysia's payment market. The country has a population of 32 million, diverse cultures, and stable economic growth. 70% of residents support the transition to a cashless society, 40% of the population uses digital wallets, and the government provides financial incentives to promote financial inclusion. Online banking accounts for 50% of transaction volume in the market for major payment service provider Adyen, demonstrating high consumer trust in online financial services. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/asiaPacific/SG/index.md): Introduces the characteristics of Singapore's payment market, including its role as a global financial hub, thriving e-commerce, high mobile adoption, and diverse payment methods. Singapore is one of the world's largest financial centers, with an extremely business-friendly environment and extensive international connections, 55% of transactions are cross-border, smartphone penetration is about 90%, and cards are the most popular payment method with 77 million cards in circulation. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/asiaPacific/HK/index.md): Describes the coverage of Hong Kong's payment market. Supports QR code payments (such as AlipayHK, WeChat Pay HK), e-wallets (Octopus, PayMe, etc.), credit and debit cards, and cash payments. Mobile payment adoption rate is high, and the market is characterized by diversification, high security, and technological innovation. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/DE/index.md): Describes the characteristics of the German payment market, including a diversified payment ecosystem, robust banking infrastructure, rapid growth in digital payments, and thriving e-commerce. It particularly emphasizes cross-border payments facilitated by SEPA standards, strict regulatory environment, and applications of innovative payment technologies such as biometrics and blockchain. - [Coverage Countries](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/FR/index.md): Coverage country documentation introduces the characteristics of the French payment market, including widely used bank cards (such as Carte Bancaire), rapidly growing mobile payments and digital wallets, strong banking infrastructure, and diverse online payment solutions. France complies with EU PSD2 directive, focuses on payment security and consumer protection, fintech companies are developing rapidly, and cash usage is decreasing year by year. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/GB/index.md): The UK payment market is highly digitalized with non-cash payments dominant, mobile payments and digital wallets widely adopted. Credit cards, debit cards and bank transfers are extensively used, fintech companies and digital banks are thriving. E-commerce ecosystem is well-developed with rich online payment solutions and high demand for cross-border e-commerce payments. Strictly regulated by the Financial Conduct Authority (FCA) to ensure payment security and consumer protection. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/IT/index.md): Introduces the characteristics of the Italian payment market, including the widespread use of cash but rapid growth of digital payments, the popularity of debit and credit cards, the increasing popularity of contactless payments, and the rapid development of mobile payments and e-commerce. Local payment innovations such as the PagoPA system simplify public service payments, comply with EU PSD2 regulatory requirements, accelerate fintech development, and traditional banks increase their digital transformation efforts. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/ES/index.md): Spain's payment market is characterized by rapid growth in digital payments, widespread use of bank cards especially debit cards, and increasing adoption of mobile payments and digital wallets. Cash usage frequency is declining, with small payments shifting to digital methods. E-commerce is developing rapidly with diversified online payment methods and widespread application of international payment platforms. The banking sector is actively promoting digital transformation with popularized online and mobile banking services. The regulatory environment complies with EU PSD2 directive, focusing on payment security and consumer protection - [Coverage Area](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/NL/index.md): Describes the characteristics of the Dutch payment market, including high digitization, popular local payment methods such as iDEAL and debit cards, innovative payment technologies like contactless payments and Tikkie app, open banking ecosystem, e-commerce development, and reduced cash usage. The Netherlands has an efficient interbank clearing system and high payment security standards. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/SE/index.md): Sweden's payment market is close to a cashless society, with digital payments dominant and many merchants no longer accepting cash. Innovative payment technologies such as biometric and contactless payments are popular, the open banking ecosystem is active, and traditional banks are actively digitizing. E-commerce is developing rapidly, online payment solutions are diverse, and cross-border e-commerce payment demand is growing. The regulatory environment complies with EU PSD2 directive, focusing on payment security and consumer protection. Internationalization trends are obvious, - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/PL/index.md): Poland's payment market is rapidly digitizing, with reduced cash usage and rapid growth in digital and mobile payments. The BLIK payment system is widely used, and inter-bank transfers are efficient and convenient. Debit cards and contactless payments are popular, e-commerce is diverse, and online payment platforms like Przelewy24 are favored. Fintech startups are increasing, and traditional banks are accelerating digital transformation. Compliant with EU PSD2 regulations, the government promotes cashless payments. International trends are evident, - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/BE/index.md): Covers the payment market characteristics of Belgium, including widely used bank cards, Bancontact system dominance in local payments, rising mobile payment and digital wallet adoption, contactless payment popularity, diverse online payment options, and widespread use of international payment platforms. Mobile payment solutions like Payconiq are popular, with efficient inter-bank transfer systems. Complies with EU PSD2 regulations, focusing on payment security and consumer protection. Cash usage is declining. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/AT/index.md): This document describes the characteristics of the Austrian payment market, covering both traditional and innovative payment methods. Cash and debit cards are still widely used, but digital payments, contactless payments, and mobile payments are growing rapidly. Local EPS and international payment platforms are popular, online payments are diverse, and cross-border e-commerce demand is increasing. The regulatory environment complies with PSD2, focusing on security and data protection. The number of fintech companies is increasing, and traditional banks are actively transforming. - [Coverage Countries](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/CH/index.md): Describes the characteristics of the Swiss payment market, including a highly developed financial system, diverse payment methods, and growing trends in digital payments. Mobile payments and digital wallet usage are rising, contactless payments are widespread, e-commerce is developing rapidly with strong demand for cross-border payments. Although cash usage remains important, international payment platforms such as Apple Pay are also widely used. The regulatory environment is strict with emphasis on payment security, maintaining consistency with EU payment regulations. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/DK/index.md): Denmark's payment market is highly digitalized, approaching a cashless society with digital payments dominant. Online and mobile banking have high adoption rates, with electronic invoicing and automatic payments widely used. Contactless payments are popular in retail, and new technologies like biometric payments are gradually being introduced. Online payment solutions are diverse with growing cross-border e-commerce payment needs. The regulatory environment complies with the EU Payment Services Directive (PSD2) and the government actively promotes digital payments. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/NO/index.md): Norway's payment market is dominated by digital payments with minimal cash usage. Mobile payments and digital wallets are widespread, electronic banking is advanced, online and mobile banking have high adoption rates, and automatic payments are widely used. Contactless payments are common, and new technologies such as biometric payments are gradually being introduced. Online payment methods are diverse, with growing demand for cross-border e-commerce payments. Despite not being an EU member, Norway's payment regulations align with EU standards, emphasizing payment security and consumer protection. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/FI/index.md): The coverage areas module describes the characteristics of Finland's payment market, including high digitalization, low cash usage, and high mobile payment adoption. Debit cards are the primary payment method, with contactless payments being widespread. E-commerce is diverse with growing cross-border payment needs. PSD2 drives open banking ecosystems, with close collaboration between fintech and traditional banks. The regulatory environment is strict, focusing on payment security and data protection. International payment platforms like Apple Pay are popular, with local solutions expanding in - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/IE/index.md): Coverage area documentation details the characteristics of Ireland's payment market. This market is characterized by rapidly growing digital payments, including widely used bank cards, mobile payments, and digital wallets; reduced cash usage with small payments shifting to digital methods; popular contactless payments and innovative mobile payment applications like Revolut; diverse online payment methods for e-commerce and widespread use of international payment platforms; PSD2 driving financial innovation, and increased collaboration between fintech companies and traditional - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/PT/index.md): Portugal's payment market is experiencing rapid growth in digital payments, with increased card usage especially debit cards, and growing adoption of mobile payments and digital wallets. The Multibanco system and MB WAY application dominate local payments. While cash remains widely accepted, small-value payments are gradually shifting to digital methods. Online payment solutions are diversified with increased use of international payment platforms. Emerging technologies such as contactless payments and QR code payments are being progressively introduced. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/GR/index.md): Describes the characteristics of the Greek payment market, including rapidly growing digital payments, rising card usage, increasing adoption of mobile payments and digital wallets, widespread cash usage that is gradually decreasing. E-commerce is developing rapidly, international payment platforms are being used more, and contactless payments and mobile payment applications such as Viva Wallet are popular. Compliant with EU PSD2 regulations, government supports digital payments to improve tax transparency, fintech accelerates innovation, traditional banks increase - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/CZ/index.md): Covers the payment market characteristics of the Czech Republic, including digital payment growth, reduced cash usage, e-commerce development, innovative payment technologies, and regulatory environment. Details the popularity of bank cards and mobile payments, diversification of online payment solutions, application of contactless payments, and compliance with EU PSD2 directive requirements. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/RO/index.md): Covers the Romanian payment market, introducing the payment characteristics of this region. Digital payments are growing rapidly, card usage is rising, and mobile payments and digital wallets are becoming popular; cash usage remains common but is gradually decreasing. E-commerce is developing rapidly, online payment methods are diversifying, and international payment platforms are increasingly used. Innovative payment technologies such as contactless payments and mobile payment applications are gradually being introduced. Local payment preferences include bank transfers and RoPayments. The regulatory environment complies with EU - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/HU/index.md): Hungarian payment market characteristics include rising card usage, increased adoption of mobile payments and digital wallets, and reduced cash usage. The government promotes cashless payments, instant payment systems (AFR), and local mobile payment solutions such as Satispay are popular. E-commerce is developing rapidly with diversified online payment methods and increased use of international payment platforms. Contactless payments are widespread in retail, and emerging payment methods such as QR code payments are gradually being introduced. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/SK/index.md): Slovak payment market characteristics include: rising card usage, increased adoption of mobile payments and digital wallets, reduced cash usage, rapid e-commerce development, and growing popularity of contactless payments and mobile payment applications such as Google Pay and Apple Pay. Bank transfers hold an important position in online payments, with local payment methods like TatraPay being popular. The regulatory environment complies with EU PSD2 standards, focusing on payment security and consumer - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/HR/index.md): Croatia's payment market characteristics include rising bank card usage, mobile payment and digital wallet adoption, joining the Eurozone in 2023 to promote payment system modernization and accelerate payment integration with other Eurozone countries. Reduced cash usage, e-commerce development driving diversification of online payment solutions and increased use of international payment platforms. Innovative payment technologies such as contactless payments are popular in retail, and mobile payment applications are gradually being introduced. The regulatory environment complies with EU PSD2 - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/BG/index.md): Coverage area documentation introduces the characteristics of Bulgaria's payment market, including rapid growth of digital payments, widespread cash usage, diversified e-commerce development, and the introduction of innovative payment technologies such as contactless payments and mobile payments. Local payment preferences favor bank transfers, the regulatory environment complies with EU PSD2 standards, the government promotes digital payments to improve financial inclusion, and fintech accelerates innovation. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/SI/index.md): Introduces the characteristics of Slovenia's payment market, including high bank card usage, widespread adoption of mobile payments and digital wallets, reduced cash usage, diverse online payment solutions, and increased use of international payment platforms. It particularly emphasizes the popular trends of contactless payments and mobile payment applications such as Google Pay and Apple Pay, along with a regulatory environment compliant with EU PSD2 regulations, accelerated fintech innovation, and traditional banks' digital transformation - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/LT/index.md): Lithuania's payment market characteristics include: high bank card usage rate, rapid adoption of mobile payments and digital wallets; as one of Europe's fintech hubs, home to numerous innovative payment companies; reduced cash usage with digital payments dominating daily transactions; e-commerce development driving diverse online payment solutions; widespread adoption of contactless payments and instant payment systems; compliance with EU PSD2 regulatory requirements, favorable financial innovation environment; strong cross-border payment demand with high integration with EU countries' payment systems - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/LV/index.md): Coverage area documentation describes the payment market characteristics of Latvia, including rising bank card usage, increased adoption of mobile payments and digital wallets, reduced cash usage, and other trends. E-commerce is developing rapidly, international payment platforms are increasing, contactless payments and local mobile payment solutions such as Satispay are gradually becoming popular. The region complies with the EU Payment Services Directive (PSD2), focusing on payment security and consumer protection, financial technology innovation especially in mobile payments - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/EE/index.md): Estonia's payment market is highly digitalized with widespread use of mobile payments and digital wallets, supported by the e-ID system providing a secure foundation. E-commerce is developing rapidly with strong demand for cross-border payments. Fintech companies are active with ongoing exploration of blockchain technology applications. Compliant with EU PSD2 directive and government support for innovation. The country approaches a cashless society where most transactions are completed digitally. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/LU/index.md): Describes the characteristics of Luxembourg's payment market, including a highly developed financial system, widespread digital payments, strong cross-border payment demand, and application of innovative payment technologies. The region supports multi-currency payment solutions, e-commerce develops rapidly, regulatory environment complies with EU PSD2 standards, focusing on payment security and consumer protection. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/MT/index.md): Malta's payment market is experiencing growth in digital payments, with rising adoption of card payments and mobile payments. As a fintech hub in the Mediterranean region, it has attracted numerous payment and blockchain companies. Although cash is still widely accepted, usage frequency is declining, with small payments shifting to digital methods. Online payment solutions are diversified, with increased use of international payment platforms. Contactless payments are popular in retail, and mobile payment applications such as Apple Pa - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/europe/CY/index.md): The coverage areas module introduces the characteristics of Cyprus's payment market, including digital payment growth, cash usage, e-commerce development, and the application of innovative payment technologies. Bank card usage, especially debit cards, is rising, while mobile payments and digital wallets are gradually becoming popular. Despite widespread cash usage, online payment solutions are diversifying and international payment platforms are increasingly used. Contactless payments are widely adopted in retail, and mobile payments such as Apple - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/americas/US/index.md): Payment preferences for the United States region, where credit cards are the most popular payment method accounting for 40% of total transaction volume, and digital wallets such as PayPal and Apple Pay are growing rapidly in e-commerce. Debit cards remain an important payment method, especially for daily small transactions. Mobile payment adoption continues to rise, but cash remains important in certain scenarios. Merchants need to provide multiple payment options to meet market demands. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/americas/CA/index.md): Introduces the characteristics of Canada's payment market, including preferences for card payments and the popularity of digital wallets. Debit and credit cards account for 70% of total transaction volume, with Klarna being a commonly used digital wallet. Mobile payments are growing rapidly, while cash remains important in specific scenarios. Merchants need to support both international and local payment methods and provide bilingual interfaces to meet market demands. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/americas/MX/index.md): Payment methods covering the Mexico region. The Mexican market is cash-dominated, but credit cards, debit cards, and digital payments are growing rapidly. OXXO convenience store payments provide an online shopping option for consumers without bank accounts. Merchants need to support multiple payment options, including major bank cards, local payments such as OXXO and SPEI, and installment payments. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/americas/BR/index.md): Payment methods covering Brazil. Credit cards account for 30% of total transaction volume, Boleto Bancário accounts for 25%. The e-commerce market is developing rapidly, with increased usage of mobile payments and digital wallets. PIX has gained rapid popularity since its launch in 2020. Merchants need to provide multiple payment options, including international credit cards, local payment methods such as Boleto and PIX, and installment payments. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/americas/AR/index.md): Argentina's payment methods encompass both traditional and digital approaches, with credit cards accounting for 35% of transaction volume and cash still representing 25%. The e-commerce market is growing rapidly, with increased usage of digital wallets and installment payments popular due to high inflation. Merchants need to provide multiple payment options including major credit cards, local payment methods such as Rapi pago, and digital wallets, while considering exchange rate risk management. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/americas/CL/index.md): Payment methods covering the Chilean market. Credit cards and debit cards are the primary payment methods, accounting for 40% and 25% of total transaction volume respectively, with bank transfers accounting for 20%. Digital wallet usage is rising, and cash remains important in certain small transactions. Merchants should offer multiple payment options including credit cards, debit cards, bank transfers (such as Servipag), and installment payments, while optimizing online banking payment experiences to adapt to high bank account penetration rates. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/americas/CO/index.md): The coverage areas module introduces the characteristics of Colombia's payment market. Cash payments still dominate in this country, but credit card and digital wallet usage continues to grow. Main payment methods include credit cards, PSE system, cash payment networks (such as Efecty), and installment payment options. Merchants need to provide diverse payment options to adapt to consumer preferences in different regions. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/americas/PE/index.md): Peru's payment market is cash-dominated, but digital payments are growing. Main payment methods include cash (40%), debit cards (20%), credit cards (15%), and bank transfers (15%). PagoEfectivo is a local unique payment solution that supports cash and online banking payments, suitable for consumers without bank accounts or credit cards. Merchants need to provide diverse payment options such as mainstream card types, bank transfers, digital wallets, and ### Others - [Markdown](https://acquirer-api-docs-v4-en.pingpongx.com/en/article/079v1vx5/index.md) - [Custom Component](https://acquirer-api-docs-v4-en.pingpongx.com/en/article/xwq2sj6e/index.md) - [Custom Component](https://acquirer-api-docs-v4-en.pingpongx.com/en/blog/gni6e10p/index.md) - [Markdown](https://acquirer-api-docs-v4-en.pingpongx.com/en/blog/z8jr38qh/index.md) - [Demo](https://acquirer-api-docs-v4-en.pingpongx.com/en/demo/index.md) - [foo](https://acquirer-api-docs-v4-en.pingpongx.com/en/demo/40d40e2c/index.md) - [bar](https://acquirer-api-docs-v4-en.pingpongx.com/en/demo/mze6a2fk/index.md) - [Order Cancel API](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/InPersonPayments/cancel/index.md): Order Cancel API is used to cancel orders that have not yet been completed. Suitable for scenarios where customers need to cancel pending orders, supporting cancellation of orders in various states. - [POS Command Declare API](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/InPersonPayments/cmdDeclare/index.md): POS Command Declare API is used to send functional commands to POS devices, supporting summary query, settlement execution, and printing the last transaction. Through this interface, merchants can remotely control POS devices to complete various daily operational functions. - [GMC Serial Heartbeat Interface](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/InPersonPayments/gmc/heartbeat/index.md): The GMC serial heartbeat interface is used to maintain the connection status between SAAS and POS devices. It is recommended to send a heartbeat packet every 30 seconds, and continuous 3 times of no response can determine that the device is offline. The bizContent field can be empty. - [GMC Serial Payment Interface](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/InPersonPayments/gmc/pay/index.md): The GMC serial payment interface is used to complete payment transactions by communicating with POS devices through serial ports. It supports creating orders and executing payments immediately, suitable for offline payment scenarios where SAAS cash register systems integrate with POS devices. It adopts serial communication protocols and SHA256 signatures to ensure data security, and supports passing customer information and product information. - [GMC Serial Pay Query Interface](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/InPersonPayments/gmc/payQuery/index.md): The GMC serial pay query interface is used to query the status and details of payment transactions. It communicates with POS devices through serial ports and supports querying transaction status, amount, time and other details by merchant order number or PingPong transaction ID. It adopts SHA256 signature to ensure data security and is suitable for reconciliation, status confirmation and other scenarios. - [GMC Serial Query Interface](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/InPersonPayments/gmc/query/index.md): The GMC serial query interface is used to query the status and details of payment or refund transactions. Through serial port communication with POS devices, it supports querying transaction status, amount, time and other detailed information by merchant order number. It adopts SHA256 signature to ensure data security, suitable for scenarios such as reconciliation and status confirmation. - [GMC Serial Port Refund Interface](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/InPersonPayments/gmc/refund/index.md): The GMC serial port refund interface is used to initiate refund requests for completed payment transactions. Communicates with POS devices via serial port, supporting both full and partial refunds. Employs SHA256 signature to ensure data security, with refund processing time varying by payment method, typically 3-7 business days. - [GMC Serial Refund Query Interface](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/InPersonPayments/gmc/refundQuery/index.md): The GMC serial refund query interface is used to query the status and details of refund transactions. It communicates with POS devices through serial ports and supports querying refund status, amount, time and other details by merchant refund ID or PingPong refund ID. It adopts SHA256 signature to ensure data security and is suitable for refund reconciliation, status confirmation and other scenarios. - [GMC Serial Reprint Interface](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/InPersonPayments/gmc/reprint/index.md): The GMC serial reprint interface is used to reprint the receipt voucher of the previous transaction. Communicates with POS devices via serial port, suitable for scenarios where receipt printing fails or vouchers need to be reprinted. The bizContent field can be empty, defaulting to print the last transaction. - [GMC Serial Settlement Interface](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/InPersonPayments/gmc/settlement/index.md): The GMC serial settlement interface is used to trigger the POS device to perform batch settlement operations. It is typically called at the end of each business day to clear all transaction batches for the day. The bizContent field can be empty. After settlement, the POS device will print settlement vouchers. - [GMC Serial Transaction Cancel Interface](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/InPersonPayments/gmc/transactionCancel/index.md): The GMC serial transaction cancel interface is used to cancel transactions in progress. It communicates with POS devices through serial ports and cancels transactions based on merchant transaction ID. It adopts SHA256 signature to ensure data security and is suitable for scenarios such as user cancellation of payment, transaction timeout, etc. - [Single Transaction Query](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/InPersonPayments/paymentQuery/index.md): The Single Transaction Query API is used to retrieve detailed information about a specific transaction. It is suitable for scenarios that require tracking or verifying the status of a particular payment, supporting calls through transaction ID. Main functions include returning key data such as transaction status, amount, and time. - [Request Refund](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/InPersonPayments/refund/index.md): The Request Refund API is used to process refund requests for paid orders in PingPongCheckout. It applies to scenarios requiring refund services for customers and supports multiple currencies across major global markets. Through this interface, developers can specify key parameters such as refund amount and reason to achieve fast and secure fund returns. - [Refund Query](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/InPersonPayments/refundQuery/index.md): The refund query API allows merchants to retrieve the status and details of a specific refund request. Suitable for scenarios requiring tracking or verification of refund processing, supporting multiple global markets. By providing the refund ID as a key parameter, real-time information such as refund status, amount, and processing time can be obtained. - [Order Creation and Payment Interface](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/InPersonPayments/unifiedPay/index.md): The order creation and payment interface provides functions for creating orders and executing payments immediately. It is suitable for online business scenarios that require quick completion of the process from order placement to payment collection. It supports major global currencies and covers various payment methods including credit cards and local payment methods. Key parameters include merchant ID, order amount, product description, etc. Through this API, merchants can simplify the shopping process and enhance user experience. - [CAPTURE - Pre-Authorization Confirmation](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/marketplaces/mpCapture/index.md): The CAPTURE - Pre-Authorization Confirmation API is used to formally charge the pre-authorized payment amount. Suitable for scenarios where merchants need to verify buyer payment capability before shipping, supporting major global markets. By calling this API, merchants can specify key parameters such as transaction ID and amount to complete the charging process. - [Request Refund](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/marketplaces/mpRefund/index.md): The Request Refund API allows merchants to initiate refund requests. Suitable for scenarios requiring processing of consumer refund requests, supporting multiple global markets. Key features include specifying order ID, refund amount, and reason. Key parameters include order_id (order identifier), refund_amount (refund amount), and reason (refund reason). - [Marketplaces Direct API (Non-Hosted Mode)](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/marketplaces/mpUniformly/index.md): Marketplaces Direct API provides payment solutions in non-hosted mode. Suitable for e-commerce platforms that wish to directly manage payment processes, supports card payments and requires integration of risk control components to ensure transaction security. This API allows merchants to customize payment interfaces while strictly adhering to relevant security specifications. - [VOID-Preauthorization Cancellation](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/marketplaces/mpVoid/index.md): The VOID-Preauthorization Cancellation API is used to cancel preauthorization transactions that have been created but not yet captured. It applies to merchants releasing customer funds when payment completion is not needed, reducing unnecessary financial processing. Key features include specifying transaction ID to perform cancellation operations, supporting multiple currency types worldwide. Key parameters involve transaction identifiers, cancellation reasons, etc., ensuring flexibility and security in fund management. - [Create Sub-Merchant API](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/marketplaces/submerchant/insertSubmerchant/index.md): The Create Sub-Merchant API is used to create new sub-merchant accounts in the PingPongCheckout system. It is suitable for e-commerce platforms or enterprises that need to manage multiple sub-merchants. Main functions include submitting sub-merchant information and obtaining creation results. Key parameters include sub-merchant name, contact information, etc. - [Batch Update Sub-Merchant API](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/api/services/marketplaces/submerchant/updateSubmerchant/index.md): The batch update sub-merchant API is used to update multiple sub-merchant information simultaneously. It is suitable for scenarios that require large-scale adjustment of sub-merchant data, supporting submission of multiple records in a single request to improve efficiency. Main functions include modifying sub-merchant name, status, and other key information. - [Americas-APM](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/apm/hosted/americas/index.md): Various payment methods available in the Americas region and their transaction currencies, covering Brazil, Chile, Argentina, Canada, Colombia, Dominican Republic, Mexico, Peru, United States, and Uruguay. Each payment method lists supported currency units and remarks, suitable for merchants and technical personnel who need to understand payment options in various countries and regions. - [Asia-APM](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/apm/hosted/asia/index.md): The Asia-APM document lists the main online payment methods in China, Japan, Philippines, and South Korea along with their supported transaction currencies. Suitable for merchants and technical personnel who need to understand or integrate local payment solutions in these countries. China supports Alipay and WeChat, covering multiple international currencies; Japan includes convenience store payments, Pay-easy, etc.; Philippines has Dragonpay; South Korea details multiple banks and credit cards - [Europe-APM](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/apm/hosted/europe/index.md): Europe-APM documentation lists available payment methods and their transaction currencies for countries such as Andorra, Austria, Belgium, Bulgaria, Switzerland, Cyprus, and Czech Republic. It covers multiple payment options including SEPA Direct Debit, Trustly, Klarna Pay later, Paysafecard, suitable for businesses and individuals who need to understand payment methods and supported currencies by country. - [Oceania-APM](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/apm/hosted/oceania/index.md): Oceania APM payment methods guide, covering Paysafecard and Skrill payment options for Australia and New Zealand. Supports AUD and EUR transaction currencies, suitable for merchants requiring diverse payment solutions in this region. - [Non-hosted Supported APM](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/apm/nonHosted/asia/index.md): This document lists non-hosted alternative payment methods (APM) supported in South Korea, Vietnam, and Thailand, including local mainstream bank cards, e-wallets, and bank transfer services. Suitable for merchants or developers who want to understand available payment methods in specific Asian markets. - [Payment Methods List](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/APMList/index.md): The payment methods list details various payment means and their characteristics, suitable for developers and merchants who need to integrate or select payment solutions. The content covers global mainstream payment methods such as credit cards, debit cards, and multiple e-wallets, with particular emphasis on the availability of each payment method in different regions and transaction processing features. - [Arbitration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/Arbitration/index.md): Arbitration is the final stage of credit card transaction dispute handling. When pre-arbitration fails to resolve disputes, both parties can submit the dispute to credit card organizations (such as Visa or Mastercard) for formal adjudication. During the arbitration process, both parties must submit relevant evidence and documents, and the credit card organization makes a final binding decision after evaluation, based on which funds are processed. - [CreditCard](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/creditCardList/index.md): CreditCard lists supported credit card types and their detailed information. Applicable to online payment scenarios worldwide, covering major international card organizations such as Visa, MasterCard, etc. Each card type includes specific codes and enumeration values for easy system integration and identification. - [Currency Exchange](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/currencyExchange/index.md): The currency exchange table lists multiple source currencies and their supported target currencies for exchange. Suitable for scenarios requiring currency conversion, such as international payments and cross-border transactions. Key features include extensive coverage of currencies from multiple global regions, such as US Dollar (USD), Euro (EUR), Chinese Yuan (CNY), etc., and support for conversion from common currencies to niche currencies. - [Document Update Records](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/faq/index.md): Document update records summarize the release items and content descriptions for each month of 2023, including chargeback flowchart updates, 3DS enumeration value changes in asynchronous notifications and transaction query APIs, new JS-SDK-2.0 documentation and its debugging tools, adjustments to country code/transaction currency lists, new error codes, removal of transaction reconciliation API, new offline barcode payment product documentation, etc. - [Locale](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/lang/index.md): Locale defines supported languages and region codes, applicable to application scenarios requiring multi-language support. The table lists locale identifiers and API transmission values for major languages and their variants, such as de for German and en-US for American English. - [merchantTransactionId](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/merchantTransactionId/index.md): merchantTransactionId is a merchant transaction identifier used to uniquely identify each transaction of the merchant. In e-commerce and payment systems, merchants can accurately track order status and processing situations by generating unique merchantTransactionIds. This identifier is usually associated with the transactionId generated by the payment service provider to ensure effective management and tracking of transactions - [Payment Methods](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/paymentMethods/index.md): The payment methods list covers various international and local payment options, including credit cards (such as VISA, Mastercard, American Express), debit cards (such as JCB, DinersClub, Discover) and specific regional payment tools (such as Giropay, iDeal, Trustpay, My Bank, SEPA, Kakaopay), applicable - [Merchant Registration Process](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/appendix/register/index.md): Introduces the process for merchants to register and login through the PingPongCheckout official website. Suitable for global merchants to quickly create acquiring accounts and use services. New users need to fill in basic information to complete registration, and must change the password when logging in for the first time; supports both Simplified Chinese and English interface, Chrome browser is recommended for access. - [Request Order Closure](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/checkout/api/close/index.md): The request order closure API is used by merchants to actively close incomplete payment orders. It applies to scenarios such as user purchase cancellation or payment timeout. Through this API, order status can be updated in time to reduce fund freezing duration. Main parameters include order number, closure reason, etc., supporting online payment transactions worldwide. - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/americas/GT/index.md): Guatemala's payment landscape is diverse, with cash dominating the market at 50%, credit cards and debit cards accounting for 20% and 15% respectively, and bank transfers taking 10%. E-commerce is gradually growing in urban areas and among younger demographics. VisaNet is an important local payment network, and digital wallets like Tigo Money are increasing but still in early stages. Merchants need to provide multiple payment options including cash, major bank cards, bank transfers, and emerging digital payments - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/americas/HN/index.md): Honduras' payment market is cash-dominated, accounting for 55% of total transaction volume, with credit and debit card usage growing slowly at 15% each. Bank transfers account for 10%. E-commerce is in its early stages, with Tigo Money being an important mobile payment platform. Merchants need to provide multiple payment options including cash, major bank cards, bank transfers, and emerging digital payment methods. Considering the needs of unbanked consumers, flexible payment options such as installment payments are also required - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/americas/SR/index.md): Suriname's payment market is cash-dominated, accounting for 55% of transaction volume, with debit cards and credit cards accounting for 20% and 15% respectively, and bank transfers accounting for 7%. E-commerce is developing, with local banks such as DSB Bank and Hakrinbank playing important roles. Mobile payments and digital wallets are increasing but have low penetration. Merchants need to provide multiple payment options, including cash, major bank cards, bank transfers and emerging digital payment methods, and consider installment payments and - [Coverage Areas](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/covers/americas/SV/index.md): Covers the payment market in El Salvador, introducing the payment methods and characteristics of the region. Cash remains the primary payment method at 45%; credit cards, debit cards, and digital wallets account for 20%, 15%, and 15% respectively, with digital wallets growing rapidly. El Salvador is the first country to adopt Bitcoin as legal tender, and the Chivo wallet supports both Bitcoin and USD transactions. Merchants need to provide multiple payment options, including cash, mainstream bank cards, digital wallets (such as Chi - [Query Chargeback Records](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/dispute/apis/chargeback/index.md): The Query Chargeback Records API is used to retrieve chargeback information based on specified conditions. Supports filtering through parameters such as merchant ID, time range, chargeback type, and status. Returns results including detailed chargeback status and processing information. Suitable for merchants who need to monitor and manage chargeback processes. Key parameters include accId, startDate, endDate, chargebackType, and chargebackStatus - [Query Chargeback Operation Records](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/dispute/apis/chargebackTrace/index.md): The Query Chargeback Operation Records API is used to retrieve the chargeback processing history for specific transactions. By providing required parameters such as PingPong merchant store number and transaction order number, you can query detailed information including chargeback type, status, and change time. Supports MD5 or SHA256 signature methods to ensure data security. - [Query Chargeback Records](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/dispute/v4-apis/chargeback/index.md): The Query Chargeback Records API is used to retrieve chargeback information within a specific time period. It supports filtering by chargeback type and status, covering various chargeback types from retrieval requests to arbitration and different processing stage statuses. Key parameters include merchant ID, query type, time range, etc., with detailed chargeback record information included in the response. - [Query Chargeback Operation Records](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/dispute/v4-apis/chargebackTrace/index.md): The Query Chargeback Operation Records API is used to retrieve the chargeback processing history for specified transactions. By passing required parameters such as merchant shop ID and transaction order number, you can obtain detailed information including chargeback status change flow ID, chargeback type, and status. Supports MD5 or SHA256 signature methods to ensure data security. - [apmDemoResult](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/guide/bestPractices/apmDemoResult/index.md): apmDemoResult Introduces best practices for using APIs to query payment results. Suitable for scenarios requiring real-time payment status retrieval, supporting multiple payment methods such as credit cards, debit cards, etc. Key features include transaction ID validation and status update notifications, ensuring data security and accuracy. - [Integration Issues](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/guide/FAQ/integration/index.md): This document provides solutions for common issues during payment integration, including iframe failing to load checkout page, inability to redirect to APM payment page and issues encountered during APM payment. It emphasizes the importance of same-origin policy restrictions, points out the impact of correct request parameter and device type configuration on successful redirection, and provides solutions for specific payment methods in South Korea. - [Noun Convention](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/guide/nounContract/index.md): The noun convention document defines PingPongCheckout related terms and their meanings, applicable for developers to understand key concepts in API interface calls. The document covers explanations of important nouns such as merchant backend, website backend, clientId (merchant number), accId (store number), secret (key), methods to obtain this information, and introduces transactionId and merc - [Signature Convention - Dispute](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/guide/sign-dispute/index.md): Signature Convention - Dispute introduces how to verify the authenticity and data integrity of requests through MD5 or SHA256 algorithms. It applies to merchants ensuring communication security when processing disputes, with key parameters including accId and signType. Follows dictionary order assembly of signature strings and uses private keys for signing. - [Acceptance Test Scenarios](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/guide/testCase/index.md): The acceptance test scenarios documentation introduces use cases and precautions for testing payment functions using PingPongCheckout API. Suitable for developers to test transaction types such as order placement, refunds, pre-authorization in sandbox environments, ensuring key parameters are correct to improve transaction success rates. It particularly emphasizes the importance of testing in USD currency environment and how to simulate specific situations such as 3D security verification. - [GMC Serial Port MIS Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/InPersonPayments/gmcSerialPort/index.md): The GMC serial port MIS integration solution is suitable for SAAS cash register manufacturers, communicating with POS devices through serial ports to achieve payment, refund, query, heartbeat and other business functions. This solution adopts a custom serial communication protocol, supports serial communication with a baud rate of 115200, uses SHA256 signature to ensure data security, and is suitable for rapid integration in offline cash register scenarios. - [Offline Card Payment](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/InPersonPayments/offlineCardPayment/index.md): The offline card payment solution enables payment, query, and refund functions through cloud communication between SAAS cash registers and POS devices. Using REST API methods, key parameters include deviceSn, deviceModel, and cashierDeviceId to ensure transaction requests are accurately routed to designated POS terminals. Covers scenarios including instant payments and refund processing in physical stores, supporting both card swipe and NFC payment methods. - [Offline QR Code Payment](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/InPersonPayments/offlineQRCodePayment/index.md): The offline QR code payment solution enables communication between SaaS cash registers and POS devices through cloud services for payments, queries, and refunds. Using REST API methods, it supports mobile payment tools such as Alipay and WeChat. Key APIs include order creation, transaction query, refund application, and refund query. Suitable for retail scenarios, QR code validity can be customized, with a recommended setting of 5 minutes to optimize user experience. - [Accept in-person payments with Terminal](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/InPersonPayments/overview/index.md): PingPongCheckout's in-person payment solution supports building feature-rich point-of-sale integration systems, providing global multi-language support, diverse payment methods (such as credit cards and QR code payments), flexible network architecture, and unique shopping experiences. Easily manage payment terminals and transaction records through a unified management platform. Suitable for merchants who need localized payment experiences and customized terminal interfaces. - [Magento2.3.5-PPPay Plugin Installation Guide](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/magento235/index.md): Magento2.3.5-PPPay Plugin installation guide covers installation prerequisites, precautions, and detailed steps. Applicable for Magento version ≥2.3.5 and PHP version ≥7.1 environment, supporting curl and bcmath extensions. The document emphasizes the importance of monotonically increasing order numbers, and provides sandbox and production environment configuration parameters and command-line operation guide. - [Non-hosted](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/non-hosted/index.md): Non-hosted payment methods introduce integration approaches for international credit cards and local payments. Suitable for merchants with PCI qualifications who can develop their own checkout systems, supporting credit card payments globally and local payments in specific regions. Key features include risk control plugin integration, 3D verification processes, and transaction processing through the order and pay API. - [OpenCart-PPPay Plugin Installation Guide](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/opencart/index.md): Introduction to installing and configuring the PPPay plugin in OpenCart 3.8, including environment requirements, installation steps, and production environment integration process. Suitable for merchants who need to integrate payment functions, supports PHP 7.3 and above, pay special attention to order number uniqueness and monotonic increment rules to avoid status issues. - [Operation Manual](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/operation/index.md): This document describes how to configure payment link information in the PingPongCheckOut backend, including steps such as login, maintaining brand information, adding payment link details, etc. It is suitable for merchants who need to customize payment email templates and control payment link validity periods. Pay special attention to the uniqueness and length limit (64 characters) of business order numbers. - [Prestashop-PPPay Plugin Installation](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/prestashop/index.md): This document introduces the installation steps for the Prestashop-PPPay plugin, suitable for Prestashop stores version 1.7.6.6 and above. It covers installation prerequisites, specific installation process, and methods for configuring merchant parameters. It also provides integration processes for sandbox and production environments, including test card numbers, screenshot verification, and other key steps to ensure payment functionality is correctly integrated into the store. - [wordpress-PPPay Plugin Installation Guide](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/woocommerce/index.md): This document introduces how to install and configure the PPPay plugin in WordPress, applicable to WooCommerce 3.x version. Requires PHP 7.3 or higher and curl extension, and ensures the log directory is writable. During installation, environment parameters need to be set, log paths configured, and sandbox and production environment testing performed. Important matters include monotonic increment of order numbers, using separate accId for different databases, etc. - [ZenCart-PPPay Plugin Installation Guide](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/integrate/zenCart/index.md): ZenCart-PPPay Plugin Installation Guide provides detailed steps for integrating PPPay payment plugin on ZenCart platform. Compatible with ZenCart 1.7 and above versions, requires PHP 7.1 and its extensions. The document covers the entire process from file upload to environment parameter configuration, emphasizing the importance of order number uniqueness and monotonic increment. - [Platform Account Registration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/marketplaces/createAccount/index.md): The platform account registration documentation introduces the steps to register an account on the PingPongCheckout platform, including accessing the registration page, filling in personal information, email verification, and login. After successful registration, you need to select an account type and complete real-name authentication. Then you can create a store and view store information on the management page. - [Sub-Merchant Registration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/marketplaces/createSubMerchant/index.md): Sub-merchant registration functionality allows merchants to register on marketplace platforms, suitable for e-commerce platforms, service platforms, etc. Sub-merchants conduct transactions, receive payments, and withdraw funds through the platform. Registration information includes name, contact person, contact details, etc., and requires SafetyNet certification. Supports two registration methods: registration with transactions and registration through PingPongCheckout KYB API. - [Register Sub-Merchants via PingPongCheckout KYB API](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/marketplaces/createSubMerchantWithKYB/index.md): PingPongCheckout KYB API Used to create and manage sub-merchants, ensuring their legal compliance. Suitable for marketplace platforms, supporting batch addition and modification of sub-merchant information. Key parameters include sub-merchant ID, name, country, store URL, and MCC code. - [Create Sub-Merchant with Transaction](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/marketplaces/createSubMerchantWithTransactions/index.md): The create sub-merchant with transaction feature allows attaching a sub-merchant information list subOrderList when creating a transaction, automatically creating sub-merchants after transaction completion. Suitable for marketplace scenarios, key parameters include sub-merchant ID, order amount, currency, store link, etc., as well as product details such as name, unit price, and quantity. - [Overview](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/marketplaces/overview/index.md): Marketplaces is a cross-border payment solution provided by PingPongCheckout for financial institutions and e-commerce SaaS platforms, supporting one-stop payment experiences in online marketplaces, e-commerce websites, and mobile applications. Through APIs, it enables sub-merchant registration, secure processing of global payments, fund splitting and management, risk control, and reporting reconciliation functions. - [Asynchronous Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/index.md): The asynchronous notification interface is used to receive callback information for transaction-related events. It is suitable for scenarios that require real-time awareness of transaction status changes, such as transaction success, refunds, etc. Developers need to configure a publicly accessible `notificationUrl` address and ensure that the service supports receiving and parsing JSON data in HTTP POST requests. Key features include an automatic retry mechanism to handle network instability and clear HTTP response handling. - [Chargeback Reversal Notification](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/dispute/apis/eventCode/chargebackReturn/index.md): The chargeback reversal notification interface is used to receive results from banks or payment institutions regarding merchants successfully contesting chargebacks. It applies when a merchant provides evidence and receives support after handling credit card chargeback disputes initiated by customers. Key features include an asynchronous callback mechanism with event code chargebackReturn, ensuring real-time information updates. Main parameters cover transaction ID, status, and detailed reasons. - [Transaction Inquiry](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/dispute/dispatch/index.md): The transaction inquiry interface is used to handle cardholder queries regarding unrecognized transactions. When a cardholder has questions about a specific transaction on their statement, they can request transaction details from the merchant through this interface. The merchant must submit relevant transaction documents to the acquirer, which then forwards them to the issuing bank for verification. Key parameters include transaction number, occurrence date, etc., ensuring accurate information is crucial. - [Overview](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/onlinePayment/auth/index.md): PingPongCheckout API Used to handle pre-authorization and capture processes in online payments. Suitable for scenarios that require staged payment processing, such as custom products or reservation services. Key steps include authorization, pre-authorization voiding, pre-authorization void query, pre-authorization confirmation, and pre-authorization confirmation query. Main functions are implemented by setting parameters such as captureDelayHours to ensure funds are transferred from the customer's account at the correct time point - [Overview](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/onlinePayment/debit/index.md): PingPongCheckout API's debit transactions support both credit and wallet payment methods, providing Cashier and S2S integration modes. Cashier integration includes JS-SDK and Redirect modes, simplifying the development process and improving efficiency; S2S integration is more flexible but requires merchants to have PCI-DSS certification. Additionally, the API supports refund operations and asynchronous notification functions - [Quick Start](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/onlinePayment/integration/index.md): The quick start guide helps developers simplify the integration process of PingPongCheckout's online payment API. The document covers payment callbacks and order inquiry implementation, guiding users from zero to debugging completion of the entire process, and provides reference documentation support. Suitable for e-commerce websites and applications that need to quickly access secure payment solutions, ensuring smooth transactions while enhancing user experience. - [Issuer Response Codes](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/onlinePayment/IssuerResponseCodes/index.md): Issuer response codes define various status codes and their meanings returned by banks during online payment processes. They apply to different error situations encountered when processing payment requests, helping developers quickly identify issues and take corresponding actions. Each response code corresponds to specific payment failure reasons, such as insufficient account balance, expired card, etc., ensuring transparency and controllability of transaction processes. - [Offline Barcode Payment](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/onlinePayment/offlineBarcodePayment/index.md): Offline barcode payment function supports completing payments by scanning the barcode in the shopper's mobile wallet, suitable for POS systems that have integrated barcode scanners. Mainly supports Alipay and WeChat Pay, where Alipay barcodes are 16-24 digits and WeChat Pay is 18 digits. When initiating a payment request, specify the payment method and barcode value. - [Overview](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/onlinePayment/overview/index.md): PingPongCheckout The API supports storing cardholder's card information on the server-side after successful transactions, and generates a token for subsequent payments to improve checkout speed. Suitable for online payment scenarios, especially for users who need to repeatedly use the same credit card. Through the checkout page in Hosted mode, users can choose to save their card number, which will be automatically displayed and pre-filled with saved card information during next payment, thereby optimizing the checkout experience. - [Afterpay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Afterpay/index.md): Afterpay is a buy-now-pay-later payment method suitable for online merchants who want to provide flexible payment options for their customers. Key features include four interest-free installments, coverage in markets such as Australia, United States, and United Kingdom, and a simple integration process, which helps improve conversion rates and average order value. - [AkuLaku](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/AkuLaku/index.md): AkuLaku is a buy-now-pay-later payment method that primarily serves the Southeast Asian market, allowing consumers to pay in installments. This payment method can be used without a credit card and supports multiple repayment term options, providing users with a flexible and convenient payment experience, especially suitable for online shopping and small consumption scenarios. - [Alfamart](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Alfamart/index.md): Alfamart is a widely used cash payment method in Indonesia that allows users to make payments through the nationwide network of convenience stores. Suitable for consumers without bank accounts or credit cards, it supports various scenarios such as online shopping and bill payments. Key features include instant transaction confirmation and extensive geographic coverage. - [Alipay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Alipay/index.md): Alipay is a widely used online payment method in China and some Asian regions, supporting various scenarios such as web pages and mobile applications. Users can complete fast and secure payments through Alipay accounts or linked bank cards. After merchants integrate with Alipay, they can reach a broader consumer base and improve transaction success rates. - [AlipayHK](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/AlipayHK/index.md): AlipayHK is a widely used electronic payment method in Hong Kong, supporting users to make online and offline payments through mobile applications. Key features include convenient QR code payments, instant transfers, and rich localized services such as bill payments, ticket purchases, etc. It is suitable for various merchants to integrate and meet the payment needs of Hong Kong consumers. - [ApplePay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/ApplePay/index.md): Apple Pay is a secure and seamless payment method for in-app, in-store, and web payments. It uses Tokenization technology to store payment information and confirms payments through Touch ID or Face ID. When implemented in Europe, it complies with PSD2 SCA requirements. Users need to use compatible devices, Safari browser (for web payments), be located in supported regions, and have added bank cards to their App - [Apple Pay Checkout Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/ApplePay/checkout/index.md): Introduces the Apple Pay checkout integration process, including redirect checkout interaction and subscription payment integration. Suitable for merchants who need to support Apple Pay payments, covering multiple regions globally. Key features include pre-order to obtain payment URL, checkout rendering, and automatic deduction functionality in subscription payment mode. During integration, parameters such as `merchantUserId` and `createToken` need to be set to establish - [Apple Pay Merchant Certificate Configuration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/ApplePay/merchantCertificateConfiguration/index.md): This document describes how to configure Apple Pay merchant certificates for websites to achieve non-hosted Apple Pay Web integration. It is suitable for global online merchants who want to provide Apple Pay payment options through the Safari browser. The content covers the entire process from registering an Apple developer account to completing domain verification, including applying for certificates, creating merchant identifiers, and exchanging certificate information with PingPongPay. - [ApplePay API Integration - Token Decryption Mode](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/ApplePay/s2s_decryptionMode/index.md): Introduction to how to integrate ApplePay API through token decryption mode, suitable for merchants who need to comply with PCI compliance. In this mode, merchants use their own certificates to decrypt payment tokens and pass the information to PingPongCheckout to complete the payment process. Main steps include requesting order creation and payment, and handling different status codes such as SUCCESS, PROCESSING and FAIL - [ApplePay API Integration - Encrypted Token Mode](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/ApplePay/s2s_encryptionMode/index.md): Introduction to integrating Apple Pay API through the PingPongCheckout component using encrypted token mode. Suitable for merchants needing to support Apple Pay payments, covering major global markets. Key steps include transmitting encrypted tokens to the server for decryption processing to complete payments. When requesting order creation and payment, response status code `SUCCESS` indicates payment success, `PROCE - [ApplePay Integration - S2S](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/ApplePay/s2s/index.md): Introduction to integrating Apple Pay through Server To Server method to accept credit and debit card payments. Suitable for merchants who need to comply with PCI DSS requirements. Integration steps include risk control component and 3DS component integration, requesting orders and payments, etc. Supports two Apple Pay parameter passing methods. - [Apple Pay Domain Verification Guide](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/ApplePay/sdk_domain_association/index.md): The Apple Pay domain verification guide introduces how to enable Apple Pay functionality on your website. Suitable for merchants who wish to integrate Apple Pay on their website. Key steps include obtaining and deploying the verification file, ensuring correct file path, name, and content, and supporting HTTPS access. After completing the verification, Apple will automatically detect and confirm domain control rights, allowing merchants to use Apple Pay. - [ApplePay Embedded Checkout Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/ApplePay/sdk/index.md): ApplePay embedded checkout integration documentation introduces how to integrate ApplePay payment method in websites, suitable for online merchants who need to provide convenient payment experience for users. Covers multiple countries and regions globally, supports subscription payment model. Integration process includes submitting domain application, requesting pre-order to obtain accessToken, rendering embedded checkout, and setting up automatic recurring payment service. - [Argencard](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Argencard/index.md): Argencard is a local credit card brand in Argentina, affiliated with Prisma Medios de Pago company. As one of Argentina's earliest credit cards, it enjoys widespread recognition in the local market, supporting both in-store and online payments, and offering benefits such as installment payments and reward points. The card is widely accepted nationwide, applicable to retail stores, restaurants, and online merchants. For cross-border e-commerce, supporting Argencard - [AuPay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Aupay/index.md): AuPay is a convenient mobile payment method suitable for the Japanese market. Users can complete online and in-store payments through a mobile application, supporting various recharge methods and promotional activities. Key features include fast payments, security assurance, and exclusive discounts provided through partnerships with major merchants. - [Au Pay - Checkout Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Aupay/checkout/index.md): Introduction on how to accept Au Pay payments through checkout integration, suitable for the Japanese market. First, request checkout pre-order to obtain paymentUrl, then render and redirect to the checkout to complete the payment process. - [Au Pay API Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Aupay/s2s/index.md): The Au Pay API integration documentation introduces how to implement order creation and payment functions through API. It is suitable for merchants who need to support Au Pay payment methods in Japan region, providing server-to-server payment requests and redirect completion payment process. Key steps include calling the order creation and payment API and performing page redirection based on the returned paymentRedirectUrl to complete the payment. - [Au Pay-JSSDK Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Aupay/sdk/index.md): Introduction to accepting Au Pay payments by integrating Au Pay-JSSDK at the checkout. Suitable for online merchants in Japan, supporting pre-ordering through API and rendering checkout to complete payment process. Key steps include requesting checkout pre-order to obtain accessToken and using embedded JS-SDK to render checkout. - [Aura](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Aura/index.md): Aura is a Brazilian credit card brand issued by Aura Financeira, offering various types of credit cards to meet different consumer needs. Its features include flexible credit limits, installment payment options, and points reward programs, widely accepted in retail stores, supermarkets, and online shopping malls. Aura also provides a mobile app for users to manage accounts and pay bills conveniently, supporting multiple online payment scenarios. Suitable for merchants looking to attract more local consumers - [Banco do Brasil](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/BancoDoBrasil/index.md): Banco do Brasil is a payment method that primarily serves the Brazilian region. It supports online payments through various methods such as bank transfers, credit cards, and debit cards, providing users with convenient and secure payment experiences. Suitable for e-commerce, public service bill payments, and other scenarios, it has a broad user base and high market recognition. - [Bancomat Pay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/BancomatPay/index.md): Bancomat Pay is an electronic payment method suitable for payments in online and physical stores within Italy. It supports instant transfers, mobile payments, and other functions, allowing users to make direct payments through their bank accounts with the characteristics of convenience and security. - [Bancontact](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Bancontact/index.md): Bancontact is a widely used online payment method in Belgium that supports instant bank transfers. Suitable for e-commerce websites and mobile applications, providing fast and secure payment experience. Main features include: real-time transaction confirmation, high security, and extensive banking network coverage, covering almost all major banks in Belgium. - [MX Bank Transfer](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/BankTransferMX/index.md): Bank Transfer (MX) is a local bank transfer payment method for Mexico market scenarios, using local banking rails for payment processing. - [Banorte](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Banorte/index.md): Banorte is a major online payment method in Mexico that supports individuals and businesses to complete transactions through bank transfers or credit cards. It covers the entire Mexico region, providing a secure and convenient payment experience suitable for various scenarios such as e-commerce, public service payments, and more. - [BBVA Bancomer](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/BBVABancomer/index.md): BBVA Bancomer is a major online banking payment method in Mexico that allows users to make secure and convenient payments directly through their bank accounts. It is suitable for e-commerce platforms, public service payments, and various online transaction scenarios. It covers the entire territory of Mexico, supports real-time payment confirmation and refund functions, ensuring the security and efficient flow of funds during transactions. - [BCA](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/BCA/index.md): BCA is a bank transfer payment method in Indonesia that supports online payments through BCA bank accounts. Suitable for e-commerce platforms and various online services in Indonesia, providing instant transfer confirmation functionality to ensure secure and fast transaction completion. - [BDO](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/BDOOnlinePayment/index.md): BDO (Banco de Oro) is one of the largest banks in the Philippines, providing comprehensive online banking payment services. Users can conduct secure and efficient online payments, transfers, and financial transactions through their BDO bank accounts. This payment method offers advantages such as strong banking background, high security, extensive ATM network support, and is one of the most trusted payment methods in the Philippine market. - [BLIK](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/BLIK/index.md): BLIK is a mobile banking-based payment method primarily used in Poland. Users generate one-time codes through their mobile banking app to complete online payments without providing card information, ensuring secure and convenient transactions. Suitable for various scenarios including e-commerce, public service payments, and more. - [BNI](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/BNI/index.md): BNI is a payment method suitable for online and offline transactions in the Indonesia region. It supports various payment methods including bank transfers, credit cards, and debit cards. Its features include simple operation, high security, and extensive user base and acceptance in Indonesia. - [Boleto](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Boleto/index.md): Boleto is a commonly used payment method in Brazil that allows customers to complete payments through printed tickets at designated banks, ATMs, or online banking. Key features include extensive coverage in the Brazilian region, support for multiple payment channels such as physical stores and online platforms, and provision of certain payment periods. It is suitable for merchants who want to provide Brazilian users with a localized payment experience. - [Boleto Flash](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/BoletoFlash/index.md): Boleto Flash is a modern Brazilian payment method that provides instant processing and 24/7 service through QR codes or payment links. Suitable for consumers without bank accounts, it supports payments at counters, online banking, or mobile devices. Compared to traditional Boleto, Boleto Flash offers faster and more convenient payment experience, while traditional Boleto remains widely used due to its popularity and reliability. - [Book](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Book/index.md): Book is a payment method that allows users to complete online shopping through bank transfers. It is mainly applicable to European regions, especially Germany, Austria, and the Netherlands. This payment method has high security, supports real-time transaction confirmation, and provides multiple language interfaces to meet the needs of different countries and regions. - [Boost](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Boost/index.md): Boost is an e-wallet payment method that is widely used in Malaysia. Users can complete payments by scanning QR codes or entering phone numbers, supporting multiple currency settlements. Boost provides a convenient mobile payment experience suitable for various scenarios such as online shopping, dining services, and daily consumption. - [BPI](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/BPI/index.md): BPI is a widely used online banking payment method in the Philippines that supports users to make secure and fast payments directly through their bank accounts. Key features include real-time transaction confirmation, high security, and convenient operation process, suitable for scenarios requiring quick settlement in e-commerce websites and mobile applications. - [Bradesco](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Bradesco/index.md): Bradesco is a payment method provided by a major Brazilian bank, supporting online transfers, credit card and debit card payments. It is suitable for e-commerce platforms and covers the entire Brazil region. Its features include secure and reliable transactions, instant transaction confirmation, and high acceptance rate, providing merchants with a convenient payment collection solution. - [BRI](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/BRI/index.md): BRI is a payment method that supports the Indonesia region, completing transactions through bank transfers. It is suitable for online payment scenarios such as e-commerce platforms and travel services. Key features include convenient operation, high security, and support for multiple currency settlements. - [BSI](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/BSI/index.md): BSI is an electronic payment method suitable for European regions. It supports instant transfers and direct debits, providing a secure and efficient payment experience. Key features include fast settlement, low transaction fees, and compatibility with multiple banking systems, making it particularly suitable for online merchants and individual users when conducting cross-border transactions. - [Bualuang_iBanking](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Bualuang_iBanking/index.md): Bualuang_iBanking is a local online banking payment method in Thailand, designed for domestic online transaction scenarios and supported by local banking infrastructure. - [Cabal](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Cabal/index.md): Cabal is a payment card brand established by the Argentine Credit Union Federation, widely used in South American countries such as Argentina, Brazil, Uruguay, and Paraguay. It offers credit card, debit card, and prepaid card services, supporting both in-store and online payments. Features include flexible payment options, preferential interest rates, and an extensive merchant network. Cabal collaborates with international payment networks, enabling global card usage. For merchants targeting the South American market, especially SMEs, accepting Cabal - [Caixa](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Caixa/index.md): Caixa is a payment method primarily used in Brazil, supporting various payment methods including debit cards, credit cards, and prepaid cards. Its features include security and convenience, and it is widely used in online shopping, public service payments, and other scenarios. After merchants integrate with Caixa, they can reach a broader customer base and improve transaction success rates. - [International Card Integration - Checkout](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/cardIntegrationWidthCheckout/index.md): International Card Integration - Checkout module introduces how to accept credit and debit card payments by integrating PingPong Checkout, supporting mainstream card types such as VISA, MasterCard, etc. Covering global regions, it provides three integration methods: embedded JS-SDK, redirect checkout, and API, where API integration requires PCI DSS compliance. This solution simplifies the payment process and ensures PCI compliance while supporting 3D Secure. - [International Card Integration - S2S](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/cardIntegrationWidthS2S/index.md): International Card Integration - S2S explains how to accept credit and debit card payments through the checkout, supporting major card types such as VISA, MasterCard, etc. Provides global coverage and requires PCI DSS compliance. Offers embedded or redirect checkout integration methods to reduce merchant PCI burden, while API integration requires submission of PCI DSS documentation. Payment process includes risk control and 3DS verification steps, supporting immediate or manual capture of funds. - [Cartao MercadoLivre](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/CartaoMercadoLivre/index.md): Cartao MercadoLivre is a payment card launched by MercadoLibre, targeting its users and providing credit card and prepaid card services. Cardholders can enjoy cashback, interest-free installments and other benefits on the platform, and it supports in-store payments and ATM withdrawals. As part of the MercadoPago ecosystem, this card is popular in Brazil and other South American countries, helping merchants increase sales and customer loyalty - [Cash App](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/CashApp/index.md): Cash App is a mobile payment method that allows users to send, receive, and store money through their smartphones. Primarily used in the United States, it supports instant transfers, direct deposits, and Bitcoin purchases. Both merchants and individuals can utilize its convenience for transactions, completing most financial operations without requiring traditional bank accounts. - [Cencosud](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Cencosud/index.md): Cencosud credit card is a payment card issued by Cencosud Group, the South American retail giant, mainly used in countries such as Chile, Argentina, Brazil, Peru, and Colombia. Cardholders can enjoy benefits such as point rewards, exclusive discounts, and installment payments at supermarkets, department stores, and shopping centers under Cencosud (such as Jumbo, Easy, and Paris). The card also supports online payments, making it convenient for users to shop on the group's e-commerce platforms. - [CIMB](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/CIMB/index.md): CIMB is a payment method that primarily serves the Southeast Asian region, including Malaysia, Indonesia, Thailand, and others. It supports various transaction methods such as online banking transfers and credit card payments, offering high security and convenience, suitable for e-commerce and person-to-person transfers. - [CMR Falabella](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/CMRFalabella/index.md): CMR Falabella is a credit card brand of Chile's Falabella Group, widely used in Falabella's stores and other merchants. It offers benefits such as point rewards, installment payments, and special discounts, and collaborates with multiple banks to issue co-branded cards, expanding its usage scope. In recent years, CMR Falabella has launched a mobile app, making it convenient for customers to manage accounts and make payments. Supporting CMR Falabella payments - [Cartes Bancaires](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/CoBadgedCards/index.md): Cartes Bancaires is a payment method primarily used in France and its overseas territories, supporting both debit and credit card transactions. This payment method covers a wide range of business areas, from retail to online services, featuring high security and convenience. It is suitable for merchants who wish to enter the French market. - [Integration Methods](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/commonIntegration/index.md): Introduces the payment method integration process, including Cashier and S2S two modes. In Cashier mode, after pre-ordering to obtain accessToken or paymentUrl, you can choose to embed JS-SDK or redirect to cashier to complete payment; in S2S mode, directly request order creation and payment, obtain paymentUrl and redirect to wallet payment page. Suitable for scenarios requiring flexible payment function integration, covering wide regions and supporting multiple payment methods - [Cordial](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Cordial/index.md): Cordial is an Argentine credit card brand issued by Cordial Compañía Financiera S.A., offering various types of credit cards to meet different customer needs. Cordial cards feature flexible installment payment options, point reward programs, and exclusive offers, and are widely accepted in retail stores, supermarkets, and online malls in Argentina. Cordial also provides a mobile app for users to manage their accounts conveniently. - [Cordobesa](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Cordobesa/index.md): Cordobesa is a local credit card brand from the province of Córdoba, Argentina, issued by Banco de Córdoba. The card is widely used within the province, offering both credit and debit card services, supporting in-store payments, online shopping and ATM withdrawals. Cordobesa cards feature preferential interest rates, flexible installment payment options and exclusive offers for local merchants. Suitable for small and medium-sized enterprises and e-commerce platforms within Córdoba province, helping to attract local - [Cultureland](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Cultureland/index.md): Cultureland is a prepaid card payment method primarily used in the Korean market. Users can purchase Cultureland prepaid cards to recharge for online games, music, movies, and other digital content. This payment method supports multiple denominations, making it convenient for users at different consumption levels. - [DANA](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/DANA/index.md): DANA is a widely used e-wallet payment method in Indonesia that supports online shopping, bill payments, and peer-to-peer transfers. Users can recharge through bank accounts or partner outlets to enjoy convenient and secure mobile payment experiences. Key features include fast transaction confirmation, high security, and integration with multiple local service providers. - [DANA](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/DANA/danaIntegration/index.md): DANA is an e-wallet payment method suitable for Indonesia, supporting both Cashier and S2S integration modes. In Cashier mode, render the cashier after obtaining accessToken or paymentUrl through pre-order; in S2S mode, directly request order creation and payment to obtain paymentUrl and redirect to the wallet payment page. Device information and access model need to fill in corresponding numbers according to specific scenarios. - [docomo](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/docomo/index.md): docomo is a mobile payment method widely used in Japan, supporting convenient offline and online payments through mobile phones. Key features include fast, secure transactions and good compatibility with various merchants and services, suitable for multiple scenarios such as daily shopping, dining, and public service payments. - [DOKU VA](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/DOKUVA/index.md): DOKU VA is a virtual account payment method that allows users to complete payments through bank transfers. It is suitable for the Indonesian market and supports major local banks. Its features include instant arrival confirmation and convenient payment experience, making it particularly suitable for e-commerce platforms and businesses that require fast settlement. - [DOKU Wallet](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/DOKUWallet/index.md): DOKU Wallet is an e-wallet payment method suitable for online transactions in the Indonesian region. It supports multiple recharge methods such as bank transfers and convenience store top-ups, providing users with convenient and secure payment experiences. Key features include instant arrival, easy-to-use interface, and extensive application scenarios, making it suitable for various payment needs such as e-commerce, in-game purchases, and more. - [Dragonpay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/dragonpay/index.md): Dragonpay is an electronic payment method primarily serving users in the Philippines. It supports multiple payment channels, including bank transfers, online banking payments, and offline payment point payments, providing users with a convenient and secure payment experience. Suitable for e-commerce websites, travel service bookings, and various online transaction scenarios. - [DuitNow](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/DuitNow/index.md): DuitNow is an instant payment method primarily used for person-to-person and business-to-business transfers in Malaysia. It supports fast and secure fund transfers through mobile phone numbers, identity card numbers, or bank accounts, covering major banks and financial institutions in Malaysia. It features simple operation and rapid fund arrival, suitable for daily consumption, bill payments, and other scenarios. - [Efecty](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Efecty/index.md): Efecty is a widely used cash payment method in Colombia that allows users to make payments through a nationwide network of locations. Key features include instant transaction confirmation, usability without a bank account, and support for various payment scenarios such as bill payments, e-commerce, and more. - [Egg Money](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/EggMoney/index.md): Egg Money is an e-wallet payment method suitable for multiple countries and regions in Asia, supporting fast transfers, online shopping, and bill payments. Users can easily link bank cards to enjoy convenient and secure payment experiences. - [Elo](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Elo/index.md): Elo is a Brazilian domestic payment card brand that provides credit card, debit card, and prepaid card services, widely used in Brazil. This payment method is specifically designed for the local market, aligns with Brazilian consumer habits, and enables global usage through international cooperation. In recent years, Elo has actively expanded into mobile payments and contactless payments, supporting multiple digital wallets. For e-commerce and cross-border merchants targeting the Brazilian market, integrating Elo payments can enhance user experience and expand market share. - [EPS](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/EPS/index.md): EPS is an Austrian online bank transfer payment method that allows users to securely complete payments through their online banking accounts. Key features include instant transaction confirmation, high security, and extensive coverage of major Austrian banks. Suitable for e-commerce scenarios that require fast and secure payment options. - [FPX](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/FPX/index.md): FPX is an online banking transfer payment method in Malaysia that allows users to make secure and fast payments directly through local bank accounts. It is suitable for e-commerce websites, government services, and various online transaction scenarios. Key features include real-time transaction confirmation, support for multiple mainstream banks, and no need for additional registration to use. - [Game Culture](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/GameCulture/index.md): Game Culture is a payment method specifically designed for in-game purchases, supporting multiple countries and regions worldwide. This payment method allows players to purchase virtual goods and services through various channels, including but not limited to credit cards, third-party payment platforms, etc. Its main features include fast settlement, high security, and user-friendly interface design. - [GCash](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/GCash/index.md): GCash is a popular e-wallet payment method in the Philippines that allows users to make quick and secure online transactions through a mobile app. Key features include instant transfers, bill payments, mobile phone top-ups, and shopping payments. It is widely used in daily consumption scenarios such as supermarket shopping, dining services, and online platform payments. - [GooglePay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/GooglePay/index.md): Google Pay is a digital wallet technology that allows users to make payments in physical stores, apps, and online using credit or debit cards stored in their Google account. It supports facial recognition and fingerprint verification for transactions and is available for most issuing banks and countries. Usage conditions include compatible devices, supported browsers, HTTPS service, and valid SSL certificate. Android devices need to run And - [Google Pay Hosted Checkout Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/GooglePay/hosted/index.md): Google Pay hosted checkout integration supports subscription payment mode, allowing merchants to set up regular automatic deduction services for users. With extensive coverage areas, key features include completing the first payment through hosted checkout and obtaining a payment token, then using this token for subsequent automatic deductions. Key parameters such as `merchantUserId`, `createToken`, and `bizType` must be specified in the request. - [Google Pay API Integration - Token Decryption Mode](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/GooglePay/s2s_decryptionMode/index.md): Introduces the integration method for Google Pay API in token decryption mode, suitable for merchants who need to comply with PCI compliance and integrate risk control and 3DS components. This mode decrypts payment tokens using merchant certificates and passes the decrypted information to PingPongCheckout to complete the payment process. The main coverage area is global, with key features including support for dynamic 3DS verification and asynchronous notification mechanisms. - [Google Pay API Integration - Encrypted Token Mode](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/GooglePay/s2s_encryptionMode/index.md): Introduction to integrating Google Pay API through the PingPongCheckout component, implementing secure payments using encrypted token mode. Suitable for merchants requiring risk control and 3DS verification. Supports wide regional coverage, with main features including server-side decryption of tokens to complete transactions, ensuring data transmission security. - [Google Pay Embedded Checkout Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/GooglePay/sdk/index.md): Google Pay embedded checkout integration documentation introduces how to integrate Google Pay payment method in websites, covering multiple regions globally. The integration process includes submitting applications, requesting checkout pre-order and rendering embedded checkout. Subscription payment mode is supported, allowing merchants to set up regular automatic deduction services for users. Key parameters include merchantUserId, createToken and bizType - [GoPay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/GoPay/index.md): GoPay is a convenient online payment method suitable for multiple regions in Asia, especially Southeast Asia. It supports multi-currency settlement and provides functions such as instant transfers, bill payments, and mobile top-ups. Both merchants and individual users can easily integrate through APIs to enjoy low fees and high-security payment experiences. - [GrabPay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/GrabPay/index.md): GrabPay is an e-wallet payment method primarily used in Southeast Asia, supporting countries such as Singapore, Malaysia, and the Philippines. Users can make payments by linking bank cards or topping up their accounts, suitable for various scenarios including online shopping, ride-hailing services, and daily consumption. Its features include simple operation, high security, and the ability to provide various promotional activities to attract consumers. - [Hipercard](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Hipercard/index.md): Hipercard is a well-known Brazilian credit card brand operated by Itaú Unibanco Group, widely used nationwide especially in the northeast region. It supports both in-store and online payments, offering flexible payment options, points reward programs, and exclusive merchant discounts. Suitable for retail and e-commerce businesses, accepting Hipercard payments can effectively attract local consumers and improve sales conversion rates. - [iDeal](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/iDEAL/index.md): iDeal is a Dutch online bank transfer payment method that allows Dutch consumers to pay merchants directly through online banking. It covers major Dutch banks, provides secure and instant payment confirmation, requires no credit card, and is suitable for various online shopping scenarios. - [Indomaret](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Indomaret/index.md): Indomaret is a convenient cash payment method primarily used in Indonesia. Customers can complete cash payments for online orders at Indomaret convenience stores nationwide by presenting a payment code, suitable for people without bank accounts or credit cards. This payment method is simple and fast, supporting instant confirmation of receipt. - [VISA](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/InternationalCards/index.md): VISA is an international credit card payment method widely used in online and offline transactions globally. It supports multiple currency settlements and features fast convenience, security and reliability, suitable for various scenarios such as cross-border e-commerce and travel consumption. - [Itau](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Itau/index.md): Itau is an online banking payment method primarily used in Brazil, supporting users to securely and quickly complete payments through their Itau bank accounts. Suitable for various scenarios such as e-commerce, public service bill payments, featuring real-time settlement, high security, and convenience. - [K_PLUS](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/K_PLUS/index.md): K_PLUS is a commonly used local online banking payment method in Thailand, primarily for domestic digital payment scenarios through Thailand's banking network. - [Kakaopay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Kakaopay/index.md): Kakaopay is a popular Korean mobile payment method that supports online and offline payments through mobile applications. Key features include fast transfers, convenient QR code payments, and seamless integration with various services within the Kakao ecosystem. Suitable for e-commerce platforms and individual users who need to cover the Korean market. - [Klarna](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Klarna/index.md): Klarna is a popular "buy now, pay later" payment method covering over 20 countries. It supports four main payment options: Pay Now, Pay Later, Pay in Parts, and Financing. Risk checks are performed before using Klarna to ensure transaction security. - [Klarna-Checkout](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Klarna/integrationWithCheckout/index.md): Introduces how to accept payments by integrating Klarna checkout, suitable for physical e-commerce and virtual industries. Supports embedded JS-SDK and redirect checkout methods, no PCI DSS compliance required. Key parameters include billing address, shipping address, product information, etc., and the total product price must match the payment amount. Supports multiple language displays, but must match the transaction country and currency. Klarna has built-in wallet functionality, supporting payment continuation after interruption. - [Klarna-S2S](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Klarna/integrationWithS2S/index.md): Klarna-S2S is a way to accept Klarna payments through API, allowing merchants to customize the checkout page. Suitable for physical e-commerce and virtual industries, no PCI DSS compliance required. Main features include: coverage of Europe, North America and other regions, support for multiple payment methods such as installment payments; key parameters include billingAddress, shippingAddress and goods, etc., and it is necessary to ensure that the total goods - [Konbini](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Konbini/index.md): Konbini is a widely used convenience store payment method in Japan. After customers place orders online, they receive a bill with a barcode that can be paid at any participating convenience store within a specified time period. Key features include no need for bank accounts, simple operation, and extensive convenience store network coverage. - [Konbini-Checkout Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Konbini/checkout/index.md): Konbini-Checkout Integration documentation introduces how to accept Konbini payments through checkout integration. Suitable for online payment scenarios in the Japanese market, providing convenient pre-ordering and checkout rendering steps. Key features include generating `paymentUrl` and best practice guidelines. - [Konbini-API Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Konbini/s2s/index.md): The Konbini-API integration documentation introduces how to integrate Japanese convenience store payment methods through API. It is suitable for applications that need to support Japanese local payment scenarios. The main steps include calling the order and payment API, obtaining the redirect URL, and guiding users to the specified page to complete the payment. - [Konbini-JSSDK Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Konbini/sdk/index.md): Konbini-JSSDK integration introduces how to accept convenience store payments in Japan through API requests and JS-SDK checkout rendering. The main steps include requesting pre-order to obtain accessToken and embedding JS-SDK according to the integration document to render the checkout. Suitable for online merchants who wish to provide offline payment options for users. - [Korea Bank Transfer](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/KoreaBankTransfer/index.md): Korea Bank Transfer Introduces online payment methods of major Korean banks. Suitable for e-commerce platforms and various online services, supporting instant transfers and credit card payments. Covers the entire South Korea region and is widely popular due to its convenience and security. - [Korea Cards](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/KoreanCards/index.md): Korean card payment method supports online payments using credit and debit cards issued locally in South Korea. Suitable for transactions with Korean merchants or consumption within South Korea, featuring convenience and security. Mainly covers the region of South Korea and supports cards issued by multiple major banks. - [Local Cards Korea](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/KoreanCards/localCardKoreaintegration/index.md): Local Cards Korea Supports local Korean bank card payments, suitable for scenarios requiring access to Korean local bank payments. Integration methods include Cashier and S2S modes. In Cashier mode, render the page after obtaining accessToken or paymentUrl through pre-order; in S2S mode, directly request order creation and payment to obtain paymentUrl. Note that S2S mode requires specifying specific local - [Krungsri_Online](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Krungsri_Online/index.md): Krungsri_Online is one of Thailand's local online banking transfer methods, used in domestic online payment scenarios and processed through local banking rails. - [LinkAja](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/LinkAja/index.md): LinkAja is a payment method launched by China Mobile, suitable for China Mobile users to make online and offline payments in mainland China. Its main features include convenient mobile phone number binding, fast payment process, and extensive merchant support coverage. - [Magna](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Magna/index.md): Magna is a payment card brand issued by the Cencosud Group in Chile, primarily used in retail stores under the group such as Paris department stores and Jumbo supermarkets. Cardholders can enjoy exclusive discounts, point rewards, and flexible installment payment options, with online payment support. In recent years, Magna has expanded its acceptance scope, partnering with more third-party merchants to increase card usage flexibility, making it suitable for retailers and e-commerce platforms looking to attract local Chilean consumers - [Mandiri](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Mandiri/index.md): Mandiri is a widely used payment method in Indonesia, supporting bank transfers and e-wallets. It is suitable for online shopping, bill payments, and various e-commerce transactions. Key features include real-time arrival, security and reliability, and user-friendly interface. - [MBway](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/MBway/index.md): MBway is an instant payment method that primarily serves bank customers in the French region. Users can quickly complete transfers and payments through mobile applications or online banking, supporting various scenarios such as online shopping and bill payments. Its features include simple operation, high security, and fast processing speed. - [MCash](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/MCash/index.md): MCash is a convenient mobile payment method that primarily serves the Southeast Asian region. Users can complete quick and secure transfers, top-ups, and bill payments through mobile applications. It supports multiple currency settlements and provides real-time transaction notifications with 24/7 customer service. - [merPay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/merPay/index.md): merPay is an electronic payment method suitable for the Japanese market, supporting online shopping, bill payments, and personal transfers. Users can easily complete payments through a mobile app, featuring simple operation and high security, while offering various promotional activities to attract consumers. - [Mobile Payments Korea](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/MobilePayments/index.md): Mobile payments are widely used payment methods in South Korea, supporting transactions through smartphone applications. Suitable for online shopping, offline retail, and service payment scenarios. Key features include convenience, security, and seamless connection with bank accounts or credit cards. Available nationwide in South Korea, supporting multiple mainstream mobile payment applications such as KakaoPay and Naver Pay. - [Mobile Pop](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/MobilePop/index.md): Mobile Pop is a mobile payment method suitable for online shopping and instant transfers. Key features include a fast and convenient payment experience, support for multiple cryptocurrencies, and extensive coverage in the Asia region. Users can complete transactions by scanning QR codes or entering payment codes without carrying physical wallets. - [Multibanco](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Multibanco/index.md): Multibanco is a widely used payment method in Portugal that supports payments through ATM, online banking, or mobile applications. Users can complete payments using the reference code generated by Multibanco within a specified time period. This payment method is suitable for e-commerce transactions and is particularly popular among users without credit cards. - [Mybank](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Mybank/index.md): Mybank is a payment method based on the Alipay platform, suitable for use in China. Key features include support for large transactions, fast fund transfers, and seamless integration with the Alibaba ecosystem. Merchants can provide consumers with flexible and diverse payment options through Mybank, enhancing user experience. - [My Bank Transfer (KR)](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/MyBankTransferKR/index.md): My Bank Transfer (KR) is a local bank transfer method built on South Korea’s mature online banking and clearing infrastructure. It is commonly used in domestic digital payment scenarios and aligns with established banking payment habits in the Korean market. - [Nativa](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Nativa/index.md): Nativa is a local payment card brand issued by Banco de la Nación Argentina (Argentina's national bank), providing credit and debit card services widely used for daily consumption, online shopping, and ATM withdrawals. The card is highly trusted and widely accepted nationwide in Argentina, known for its favorable interest rates and flexible payment options. For merchants in Argentina, especially e-commerce platforms, supporting Nativa payments helps attract more local consumers and improve sales conversion rates. - [Naverpay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Naverpay/index.md): Naverpay is a mainstream online payment method in South Korea that supports users to make secure and convenient payments through their Naver accounts. It is suitable for e-commerce websites and mobile applications, providing a fast checkout experience. Key features include support for multiple payment methods such as credit cards, bank transfers, etc., and coverage throughout South Korea. - [Naverpay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Naverpay/naverpayIntegration/index.md): Naverpay is a payment method suitable for the Korean market. It supports both Cashier and S2S integration modes. In cashier mode, render the cashier after obtaining accessToken or paymentUrl through pre-order; in S2S mode, directly request order creation and payment to obtain paymentUrl and redirect to the wallet payment page. Device information and access model need to be filled according to specific scenarios. - [Octopus](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Octopus/index.md): Octopus is a contactless smart card payment method widely used in Hong Kong for public transportation, retail stores, and public services. It supports quick small-amount payments without requiring a signature, making it convenient and fast. Users can recharge through multiple channels and enjoy discount offers from certain merchants. - [Payment Methods](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/overview/index.md): The payment methods introduction document provides an overview of various payment options, including credit cards, debit cards, e-wallets, and bank transfers. Each payment method is detailed with its applicable regions, transaction process, fee structure, and security features. This document is suitable for merchants and technical personnel who wish to understand and integrate different payment solutions into their services. - [OVO](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/OVO/index.md): OVO is a widely used e-wallet in Indonesia, suitable for various scenarios such as online shopping, bill payments, and offline transactions. Users can utilize the service by linking bank accounts or direct top-ups, supporting QR code payments and transfer functions, providing convenient and secure payment solutions for individuals and merchants. - [OXXO](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/OXXO/index.md): OXXO is a widely used cash payment method in Mexico. Consumers can complete payments at any OXXO convenience store by providing the generated barcode or reference number. This payment method is suitable for users without bank accounts or credit cards, offering high popularity and convenience. - [P24](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/P24/index.md): P24 is an online bank transfer payment method primarily used in Poland, allowing users to make secure and fast payments directly through their bank accounts. Suitable for e-commerce and online service providers who want to offer localized payment experiences to Polish customers. Major supported banks include PKO Bank Polski, mBank, etc. - [PagBank](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/PagBank/index.md): PagBank is a popular digital banking payment method in Brazil that supports users to make online payments through their accounts. Main features include fast transfers, bill payments, and mobile phone top-ups. It is suitable for various scenarios such as e-commerce platforms and in-app purchases, providing users with convenient and secure payment experiences. - [Pago Efectivo](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/PagoEfectivo/index.md): Pago Efectivo is a cash payment method primarily used in Peru that allows consumers to complete online shopping payments through designated physical locations such as banks, pharmacies, or convenience stores. This payment method is particularly suitable for users without bank accounts or credit cards, providing a convenient and secure transaction method. - [Paidy](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Paidy/index.md): Paidy is a Japanese credit payment method that allows consumers to buy now and pay later when shopping online. Suitable for e-commerce platforms looking to improve conversion rates and expand their customer base. No credit card required, users can complete registration by providing only a phone number and email address. Key features include a fast checkout process, no additional fees, and widespread merchant acceptance. - [papara](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/papara/index.md): Papara is an e-wallet payment method that primarily serves the Turkish market. It supports various payment scenarios including instant transfers, bill payments, and online shopping. Users can easily manage their accounts through the mobile app and enjoy convenient and secure payment experiences. - [Pay-easy](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Pay-easy/index.md): Pay-easy is a convenient online payment method suitable for bank transfers in Japan. Users can easily complete bill payments, tuition fees, and other daily financial transactions through this service. Its main features include simple operation, support for multiple banks, and real-time arrival, providing users with a safe and reliable payment experience. - [Pay-easy Checkout Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Pay-easy/checkout/index.md): Introduces how to accept Pay-easy payments through checkout integration, suitable for merchants who want to provide convenient online payment options in the Japanese market. The document details specific steps from requesting pre-orders to rendering the checkout, and provides best practice guidelines to ensure smooth integration. - [Pay-easy API Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Pay-easy/s2s/index.md): The Pay-easy API integration documentation provides an API integration guide for using Pay-easy payments in Japan. By calling the create order and pay API, merchants can obtain the payment redirect link paymentRedirectUrl and guide users to complete the payment process at that link. Suitable for online merchants who need to support bank transfer payment methods. - [Pay-easy JSSDK Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Pay-easy/sdk/index.md): Introduction on how to accept PayPay payments by integrating Pay-easy JSSDK on your website. Suitable for merchants who want to provide convenient payment options in the Japanese market. This document details the specific steps from requesting cash register pre-order to rendering the cash register, including obtaining accessToken and best practice guidelines for using embedded JS-SDK. - [Pay By Bank](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/PayByBank/index.md): Pay By Bank is a direct bank transfer payment method that allows users to securely and quickly complete online payments through their bank accounts. Mainly applicable to European regions, it supports instant payment confirmation and high security standards. No additional registration or storage of sensitive information required, suitable for various e-commerce platforms and service providers. - [Pay By Bank - Checkout Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/PayByBank/checkout/index.md): Introduction on how to accept Pay By Bank payments through checkout integration. Suitable for merchants who want to provide direct bank payment options in Europe, supporting multiple currencies and languages. First request checkout pre-order to obtain paymentUrl, then render and redirect to the checkout page according to the integration guide to complete the transaction process. - [Pay By Bank-API Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/PayByBank/s2s/index.md): Pay By Bank-API integration supports direct bank payments. Suitable for online merchants who need to provide convenient and secure payment options. Key features include coverage of multiple European countries, placing orders and payments through API, and redirecting to complete the payment process after obtaining the paymentRedirectUrl. - [Pay By Bank-JSSDK Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/PayByBank/sdk/index.md): Introduction on how to accept Pay By Bank payments by integrating JSSDK. Suitable for merchants who need to directly embed bank payment options in their website or application. Main steps include requesting cash register pre-order to obtain accessToken, and using embedded JS-SDK to render the cash register interface. This payment method covers regions such as the UK, providing secure and convenient fund transfer services. - [PayCash](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/PayCash/index.md): PayCash is a fast and convenient online payment method suitable for scenarios requiring instant transaction confirmation and person-to-person transfers. It supports use in over 100 countries and regions worldwide, with main features including zero handling fees, real-time arrival, and high security. - [PAYCO](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/PAYCO/index.md): PAYCO is a widely used mobile payment method in South Korea, supporting online shopping, bill payments, and person-to-person transfers. Users can easily complete payment operations through mobile applications, featuring convenience and high security. After merchants integrate PAYCO, they can provide consumers with diverse payment options and enhance user experience. - [Payconiq](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Payconiq/index.md): Payconiq is a convenient mobile payment method primarily used in Belgium and Luxembourg. Users can quickly and securely conduct online or face-to-face transactions through a mobile application. Its features include instant transfers, bill payments, and support for multiple currencies. Suitable for various scenarios such as person-to-person transfers, shopping payments, and more, providing an efficient and secure payment experience. - [Paymaya](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Paymaya/index.md): Paymaya is the leading digital financial services platform in the Philippines, providing e-wallet and online payment solutions. Users can perform fast and convenient online and offline payments, transfers, bill payments, and other services through Paymaya. The platform supports multiple recharge methods, offers high security and wide merchant acceptance, making it an important mobile payment tool in the Philippine market. - [Paynow](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Paynow/index.md): Paynow is a convenient online payment method suitable for the Singapore region. It supports instant transfer payments for individuals and businesses through bank accounts or participating bank applications. Its features include fast transaction confirmation, high security, and user-friendly interface. - [PayPal](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/PayPal/index.md): PayPal is a globally widely-used online payment method that supports fast and secure transactions for both individuals and merchants. It is suitable for various scenarios including e-commerce websites, mobile applications, and cross-border payments. Key features include a well-established user account system, support for multiple currency conversions, and buyer-seller protection mechanisms. It covers regions almost worldwide, with particularly high penetration rates in North American and European markets. - [PayPay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/PayPay/index.md): PayPay is a convenient mobile payment method that is widely used in Japan. Users can complete payments by scanning QR codes, supporting various consumption scenarios both online and offline. This payment method features simple operation and fast transaction speed, and cooperates with multiple banks and financial institutions to ensure fund security and service stability. - [PayPay-Checkout Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/PayPay/checkout/index.md): Introduces how to accept PayPay payments by integrating with the checkout, suitable for the Japanese market. Main steps include requesting checkout pre-order to obtain paymentUrl, and rendering the checkout to complete the payment process. Follow best practices to ensure smooth integration. - [PayPay API Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/PayPay/s2s/index.md): The PayPay API integration documentation explains how to implement order creation and payment functionality through API. Suitable for merchants who want to provide convenient mobile payment options in the Japanese market, supporting the entire process from order request to user payment completion. Key steps include calling the order creation and payment API and handling redirects to complete payment. - [PayPay-JSSDK Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/PayPay/sdk/index.md): This document introduces how to accept PayPay payments in Japan by integrating PayPay-JSSDK. First, you need to request a cash register pre-order to obtain an accessToken, then render the embedded JS-SDK cash register interface according to the integration documentation. Following the best practices guide can ensure a smooth integration. - [Paypo](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Paypo/index.md): Paypo is Poland's leading buy now, pay later (BNPL) payment solution that provides consumers with flexible installment payment options. It supports 30-day interest-free deferred payments and installment services ranging from 4 to 9 periods. Through a simplified online payment process, Paypo offers convenient and secure payment experiences for Polish e-commerce, helping merchants improve conversion rates and enhance customer shopping experiences. Transaction amount ranges from 10 PLN to 8,000 PLN. - [Paysafecard](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Paysafecard/index.md): Paysafecard is a prepaid online payment method that allows users to make secure online payments by purchasing physical or electronic cards. Suitable for consumers who are unwilling or unable to use bank accounts or credit cards. Widely used in Europe, North America, and parts of Asia, supports multiple denominations, providing an anonymous and convenient payment experience. - [Paysera](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Paysera/index.md): Paysera is an e-wallet payment method widely used in European regions. Users can conveniently perform online shopping, transfers, and receive payments. It supports multiple currencies and provides a secure and convenient payment experience. Main features include fast transaction confirmation, low fees, and easy-to-integrate API interfaces. - [Payso](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Payso/index.md): Payso is a popular mobile payment solution in Hong Kong that supports users to make convenient online and offline payments through smartphones. Key features include fast payment, secure encryption, multi-scenario applicability, and more. It is widely used in retail, catering, transportation, and online e-commerce sectors, providing users with an efficient digital payment experience. - [Pay with iyzico](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/PayWithIyzico/index.md): Introduces iyzico payment method, an online payment solution widely used in Turkey and surrounding regions. Supports multiple payment methods such as credit cards, debit cards, and installment payments, featuring high security and convenience. Suitable for e-commerce website integration, helping businesses quickly access diverse payment options to enhance user experience. - [Permata](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Permata/index.md): Permata is an online bank transfer payment method that supports the Indonesian region. It is suitable for users who want to make secure and fast payments directly through their bank accounts. Main features include real-time transaction confirmation, support for multiple currencies, and provision of detailed transaction records, ensuring the security and transparency of every transaction. - [PicPay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/PicPay/index.md): PicPay is a popular Brazilian mobile payment method that supports individual and business users to make quick and secure fund transfers through mobile applications. This payment method allows users to bind bank cards or credit cards, and complete payments by scanning QR codes. PicPay also provides services such as bill payment and mobile phone top-up, covering the entire Brazil region, making it an ideal choice for online shopping and daily consumption. - [PIX](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/PIX/index.md): PIX is an instant payment method primarily used in Brazil. It enables fast transfers and payments between individuals and businesses through QR code generation or keys. It supports 24/7 operations with low transaction costs, suitable for various scenarios such as online shopping and bill payments. - [Presto](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Presto/index.md): Presto is a private label credit card from Colombia, launched by Grupo Éxito retail group, mainly used in supermarkets, department stores and other retail outlets under the group. Cardholders can enjoy exclusive discounts, points rewards and flexible installment payments, and support online payments. In recent years, Presto has expanded its scope of use, cooperated with more merchants, and increased the practicality of the card. Suitable for retailers and e-commerce platforms in the Colombian market to attract local - [PromptPay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/PromptPay/index.md): PromptPay is an online banking payment method in Thailand, developed and regulated by the Bank of Thailand. Merchants display QR codes for customers to scan using participating banks' applications or upload QR code screenshots to complete payments. PromptPay supports mobile phone numbers, national ID numbers, business registration numbers, and digital wallet numbers as user identification methods, enabling inter-bank transfers. This payment method simplifies the payment process, improves payment efficiency, and ensures transaction security. - [PSE](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/PSE/index.md): PSE is an online payment method targeting the Colombian market, allowing users to make payments directly through their bank accounts. Key features include support for multiple local banks, real-time transaction confirmation, and high security. Suitable for e-commerce platforms and merchants who want to provide convenient payment options for Colombian users. - [Qris](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/QRIS/index.md): Qris is a QR code-based payment method primarily used in the Indonesian market. It supports multiple e-wallets and banking applications, allowing users to complete payments by scanning QR codes provided by merchants. Its features include convenience and speed, wide compatibility, and enhanced security measures. - [RabbitLINEPay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/RabbitLINEPay/index.md): RabbitLINEPay is a payment method that combines Rabbit Card and LINE Pay, primarily used in Japan and Thailand. It supports online shopping, offline payments, and transfer functions, allowing users to complete payments by scanning QR codes or barcodes. Additionally, it provides a points reward mechanism to encourage frequent use. - [Rapi Pago](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/RapiPago/index.md): Rapi Pago is an Argentine online payment method that allows users to make quick and secure payments through bank accounts or prepaid cards. It is suitable for e-commerce platforms, public service payments, and other scenarios. Key features include instant transaction confirmation and extensive bank network support. - [RCBC](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/RCBCOnlinePayment/index.md): RCBC (Rizal Commercial Banking Corporation) is an online banking payment method provided by one of the major banks in the Philippines. Users can make secure and convenient online payments and transfer services through RCBC bank accounts. This payment method features high security, instant arrival, and simple operation, and is widely used in e-commerce, bill payment, and other scenarios. - [Rakuten Pay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Rpay/index.md): Rakuten Pay is an electronic payment method launched by the Rakuten Group, suitable for the Japanese market. It supports various scenarios including online shopping, in-store payments, and mobile payments. Users can complete payments through smartphone applications, enjoying convenient and secure payment experiences. - [RuPay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/RuPay/index.md): RuPay is India's domestic payment card network, providing credit card, debit card, and prepaid card services. It is widely used for in-store payments, online shopping, and ATM withdrawals. Its features include low fees, extensive merchant networks, and India-specific services, supporting contactless payments and mobile payments, and integrating with multiple digital wallets. For merchants targeting the Indian market, especially e-commerce platforms, supporting RuPay payments helps attract local customers and expand market share. - [SAMSUNGPAY](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/SAMSUNGPAY/index.md): SAMSUNGPAY is a convenient mobile payment method suitable for Samsung phone users to make payments at online and offline merchants that support this service. Key features include fast and secure transaction processing, extensive coverage of the Korean market, and deep integration with the Samsung device ecosystem, providing biometric authentication methods such as fingerprint recognition to ensure transaction security. - [Santander](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Santander/index.md): Santander is a payment method that primarily serves Spain, Brazil, and some European and Latin American countries. It supports various payment methods including online banking transfers, credit cards, etc., and is suitable for scenarios such as e-commerce shopping and public service payments. Its features include security and reliability, simple operation, and the ability to provide users with fast and convenient payment experience. - [Satispay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Satispay/index.md): Satispay is a convenient mobile payment method that primarily serves the Italian market. Users can directly make payments, receive money, and transfer funds through their mobile app, supporting various consumption scenarios such as retail shopping, public service payments, etc. Its features include instant arrival, no need for additional hardware, and providing a secure transaction environment. - [Sencillito](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Sencillito/index.md): Sencillito is a convenient online payment method suitable for multiple countries in Latin America. Users can make quick payments through various methods such as bank transfers or credit cards. This payment method supports both one-time payments and subscription payment models, providing a secure and efficient transaction experience. - [SEPA](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/SEPADirectDebit/index.md): SEPA is Europe's unified payment system that simplifies cross-border euro payments. It mainly includes two models: SEPA Direct Debit (SDD) and SEPA Credit Transfer (SCT). SDD allows payees to directly debit funds after obtaining authorization, suitable for consumer and personal transactions, supporting no-reason refunds within 8 weeks and 13-month unauthorized transaction追溯. SCT is initiated by the payer, irreversible after confirmation, requires separate authorization and has no unilateral refund mechanism. - [SEPA Direct Debit - Checkout Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/SEPADirectDebit/checkout/index.md): Introduces how to accept SEPA Direct Debit payments by integrating checkout, suitable for direct debits from bank accounts within the European Economic Area. First request checkout pre-order to obtain paymentUrl, then redirect to checkout according to integration documentation to complete payment process. Following APM integration practices can optimize user experience. - [SEPA Direct Debit API Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/SEPADirectDebit/s2s/index.md): SEPA Direct Debit API integration provides a payment method to place orders and make payments through the API. Suitable for businesses within the European Economic Area, supporting direct debit payments. Key steps include requesting API to place order and pay, obtaining the `paymentRedirectUrl` and redirecting to that address to complete the payment. - [SEPA Direct Debit - JSSDK Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/SEPADirectDebit/sdk/index.md): Introduction to accepting SEPA Direct Debit payments by integrating JS-SDK. Suitable for merchants in the European Single Euro Payments Area, supporting secure and convenient processing of bank direct debit transactions. The document details the steps from requesting checkout pre-order to rendering the checkout, including obtaining accessToken and best practices for using embedded JS-SDK. - [ServiPag](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Servipag/index.md): ServiPag is a widely used payment method in Chile that allows users to complete bill payments through online platforms or physical outlets. It supports various payment types such as public utility bills, credit card repayments, etc., providing convenient payment solutions for both individuals and businesses. - [ShopeePay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/ShopeePay/index.md): ShopeePay is an e-wallet payment method primarily used on the Shopee e-commerce platform and its partners. Supported regions include Southeast Asian countries such as Indonesia, Malaysia, and the Philippines. Users can enjoy fast and convenient payment experiences and participate in various promotional activities and discounts. - [Skrill](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Skrill/index.md): Skrill is a global online payment method that supports more than 100 countries and regions, providing fast and secure online transfer services. Users can receive and make payments through email addresses, support multiple currencies, and link credit cards, debit cards, and bank accounts. Key features include instant payment confirmation, low fees, and multilingual customer service, suitable for various scenarios such as e-commerce and personal transfers. - [SPEI](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/SPEI/index.md): SPEI is an instant bank transfer payment method in Mexico. Suitable for individuals and business users who want to achieve fast and secure transfers within Mexico. Main features include real-time arrival, multi-currency support, and extensive banking network coverage, ensuring efficient and convenient fund flow. - [Tarjeta Naranja](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/TarjetaNaranja/index.md): Tarjeta Naranja is Argentina's leading credit card brand, offering innovative credit solutions and an extensive merchant network. It supports installment payments, zero-interest financing, and virtual card options for online and mobile payments. Its mobile app makes it convenient for users to manage accounts and payments. Accepting this payment method helps attract Argentine consumers, especially in e-commerce. - [Tarjeta Shopping](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/TarjetaShopping/index.md): Tarjeta Shopping is a well-known credit card brand in Argentina, issued by Tarshop S.A., specifically designed for shopping consumption. The card offers flexible installment payment options and is widely accepted in Argentine retail stores, supermarkets, and online malls. Cardholders can enjoy various promotions and discounts, including exclusive offers from specific merchants. Additionally, Tarjeta Shopping has launched a mobile app to facilitate account management - [Teen Cash](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/TeenCash/index.md): Teen Cash is a prepaid card payment method specifically designed for teenagers, primarily used in North America. This payment method allows parents to set spending limits and view transaction records for their children to help manage their financial behavior. It supports online shopping and consumption at certain physical stores, making it particularly suitable for families who wish to cultivate their children's financial awareness. - [Thailand Banks](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/ThailandBanks/index.md): Thailand Banks is an aggregated page for local Thai bank payment methods, allowing users to view and switch among multiple bank channels in a single page. - [T money](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Tmoney/index.md): T money is an electronic wallet payment method widely used in Japan for public transportation, retail stores, and online shopping. Users can recharge and make payments through mobile apps or physical cards, supporting NFC technology for quick transactions. Key features include high convenience, good security, and wide popularity, making it suitable for daily small payment scenarios. - [TNGeWallet](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/TNGeWallet/index.md): TNGeWallet is an e-wallet payment method primarily used in Malaysia. It supports users to complete online shopping, money transfers, and bill payments through mobile applications. This payment method features security and convenience, making it suitable for various online transaction scenarios. - [TOSS](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/TOSS/index.md): TOSS is a popular online payment method in South Korea that supports multiple payment methods such as credit cards, bank transfers, etc. It is suitable for e-commerce websites and mobile applications, providing a convenient payment experience. It covers major banks and financial institutions in South Korea and supports instant payment confirmation and refund functions. - [Troy](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Troy/index.md): Troy is a payment method primarily used in Turkey, supporting both debit and credit card transactions. It applies to various scenarios such as online shopping and bill payments. It features fast settlement and secure reliability. After merchants integrate with Troy, they can attract more local Turkish consumers. - [TrueMoney Wallet](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/TrueMoneyWallet/index.md): TrueMoney Wallet is an electronic wallet payment method primarily used in Thailand and some Southeast Asian countries. It supports users to complete online shopping, bill payments, and transfers through mobile applications. This payment method features convenience and speed, suitable for various scenarios such as e-commerce platforms and in-app purchases, and provides multiple language versions to meet the needs of different users. - [Trustly](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Trustly/index.md): Trustly is an instant online bank transfer payment method that allows consumers to make payments directly from their bank accounts. Key features include no registration required, fast and secure transactions, and multi-currency support. Suitable for e-commerce platforms looking to provide a seamless payment experience. Covers Europe and North America, particularly suitable for merchants requiring efficient transaction processing. - [Twint](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Twint/index.md): Twint is a popular mobile payment method in Switzerland that allows users to make quick and secure transfers and payments through a smartphone app. It is suitable for various scenarios such as online shopping, in-store payments, and person-to-person transfers. It supports real-time transaction confirmation, eliminating the need to carry cash or bank cards, and provides multi-language services covering the entire Swiss region. - [UnionBank](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/UnionBankOnlinePayment/index.md): UnionBank is one of the leading digital banks in the Philippines, providing convenient online banking payment services. Users can make fast and secure online payments, transfers, and bill payments through their UnionBank accounts. This payment method is known for its innovative digital banking solutions, high security standards, and user-friendly interface, and is widely used in e-commerce and online transaction scenarios. - [UnionPaySecurePay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/UnionPaySecurePay/index.md): UnionPaySecurePay is a secure payment solution provided by China UnionPay, suitable for online and mobile payment scenarios within China. It supports multiple bank card types, ensures transaction security through encryption technology, simplifies the payment process, and improves payment success rates. Merchants can easily integrate this payment method to reach a wide range of Chinese consumers. - [UPI](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/UPI/index.md): UPI is an instant payment system used for inter-bank fund transfers within India. It supports fast and secure transactions through mobile numbers or virtual payment addresses without requiring sensitive bank information. Widely used in various scenarios including person-to-person transfers, online shopping, and bill payments. - [Venmo](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/Venmo/index.md): Venmo is a convenient mobile payment service that allows users to pay friends or merchants through a mobile app. Primarily used in the United States, it supports instant transfers, bill splitting, and online shopping. Its features include simple operation and strong social functionality, allowing users to easily add friends and view transaction records. - [DOKU VA](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/VirtualAccount/index.md): DOKU VA is a virtual account payment method suitable for the Indonesian market. It supports users to complete payments by transferring funds to designated virtual accounts, providing a convenient online payment experience. Main features include real-time transaction confirmation, support for multiple local banks, and easy integration into merchant systems. - [VNM QR](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/VNMQR/index.md): VNM QR is a QR code-based payment method suitable for the Vietnamese market. Users complete payments by scanning QR codes provided by merchants, supporting multiple e-wallets and banking applications, providing consumers with a convenient and secure payment experience. - [WechatPay](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/WechatPay/index.md): WechatPay is a WeChat payment method suitable for PC and mobile payments in mainland China. Key features include: displaying WeChat payment QR code, supporting user scan-to-pay functionality, and real-time payment status updates. On PC, users complete payments by scanning QR codes; on mobile, WeChat payment is invoked or QR code is displayed based on browser environment. Domain must be added to WeChat H5 payment authorization and Referer header must be set. - [WeChat Pay Hosted Checkout Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/WechatPay/hosted/index.md): Introduction to WeChat Pay hosted checkout integration method, applicable to Mainland China region. Obtain payment link through API pre-order to complete payment by redirecting users to WeChat Pay page. Supports re-initiating payment for orders not paid within 48 hours. - [WeChat Pay Mini Program Payment Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/WechatPay/miniProgram/index.md): WeChat Mini Program payment integration is implemented through the unified order API, supporting payments within mini programs. Applicable to Mainland China, key features include no redirection, security mechanisms based on WeChat mini programs, standardized API call processes, and smooth and fast payment experience. Key parameters include user openid, mini program AppID, and order terminal identifier. - [WeChat Pay Server To Server Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/WechatPay/s2s/index.md): WeChat Pay Server To Server integration documentation introduces how to implement WeChat Pay through S2S method. Applicable to PC, mobile browser and Webview payment scenarios, covering mainland China. Key parameters include `device.orderTerminal` and `shopperIP`. Supports direct WeChat Pay launch or payment process handling through intermediate pages, ensuring - [WeChat Pay Embedded Checkout Integration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/WechatPay/sdk/index.md): Introduces the integration process for WeChat Pay embedded checkout, suitable for merchants in China who wish to complete payments directly within their application. Main steps include requesting pre-order to obtain accessToken and integrating SDK components to achieve seamless payment experience. - [ZIP](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/paymentMethods/ZIP/index.md): ZIP originated in Australia and is one of the most recognized consumer payment brands in the local market. It has been widely adopted across online retail and digital commerce in Australia, with strong user familiarity and broad ecosystem presence. - [dispute](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/risk/dispute/index.md): Dispute handling functionality is enabled when cardholders raise objections to payments and initiate chargebacks. Through the Disputes API, the dispute process can be automated, including steps such as retrieval requests, chargeback notification processing, and submission of defense materials. Use eventCode to determine the chargeback stage, and upload or delete relevant defense materials as needed to conduct effective defense. - [List Management](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/risk/listManagement/index.md): List management functionality supports maintaining blacklists and whitelists through APIs, categorizing users based on information dimensions such as email, email domain, card number, phone number, and shipping address. Adding to the blacklist will block payment requests from related users; while users in the whitelist can bypass regular risk control checks. Additionally, it provides interfaces for adding, querying, and batch deleting list entries. - [Overview](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/riskManger/overview/index.md) - [Risk Control Decision](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/riskManger/risk/index.md) - [3DS riskDefense Component Integration Guide](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/riskManger/riskDefense/index.md) - [safePayGuardJs](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/riskManger/safePayGuardJs/index.md) - [SecureShieldJs Component](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/riskManger/SecureShieldJs/index.md) - [Add Black/White List](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/services/blackWhiteList/add/index.md): The Add Black/White List API allows users to add black and white list entries by specifying dimensions (such as email, card number, etc.), supporting further refinement of filtering conditions by country, province, and city. Key parameters include subjectType to define list type, dataType to specify data dimension, and dataValue as the specific value. Suitable for scenarios requiring fine-grained payment risk management. - [Batch Delete Black/White List](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/services/blackWhiteList/batchDelete/index.md): The Batch Delete Black/White List API allows users to remove specific black/white list entries by specifying subjectType (White/Black) and blackWhiteIds array. This interface is located under the services module, with the path /en/notes/services/blackWhiteList/batchDelete/. Requests must use the POST method - [Paginated Query of Black/White List](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/services/blackWhiteList/queryPage/index.md): The paginated query black/white list API allows users to query entries in blacklists or whitelists based on specified conditions. Supports filtering through multiple dimensions such as email, email domain, card number, phone number, and shipping address street, and can set status and pagination parameters to obtain required data. Suitable for scenarios requiring fine-grained management of transaction security. - [FunPinPin&PingPongCheckout Configuration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/services/buildingTools/funPinPin/index.md): FunPinPin and PingPongCheckout configuration documentation, used to guide users in binding and activating PingPong payment in the shop management backend settings. Suitable for merchants who need to add credit card payment functionality to their online stores. Complete the setup by filling in account information and supported credit card types, then click the activation button. Supports major global credit cards, ensuring secure and convenient transactions. - [huaweiyun](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/services/buildingTools/huaweiyun/index.md): Huawei Cloud The API documentation introduces key functions and parameters of Huawei Cloud services, suitable for developers integrating cloud computing, storage, and network resources. Provides comprehensive API call examples and error code explanations to help users get started quickly and efficiently utilize various services of the Huawei Cloud platform. - [Leadong Shop & PingPong Checkout Configuration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/services/buildingTools/leadongshop/index.md): Leadong Shop & PingPong Checkout integration configuration guide for implementing global multi-currency online payments. Suitable for cross-border e-commerce platforms, supporting multiple payment methods such as credit cards, local payments, and providing secure transaction environment and convenient settlement services. Key parameters include merchant ID, secret key, and payment interface settings. - [shopify](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/services/buildingTools/shopify/index.md): Shopify integration guide for embedding PingPongCheckout payment solutions into Shopify stores. Supports multiple regions globally, providing secure and convenient payment processing services. Key features include multi-currency settlement, quick integration, and highly customizable options. - [Shoplus&PingPongCheckout Configuration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/services/buildingTools/shoplus/index.md): Shoplus PingPongPay configuration document introduces how to set up PingPongPay as a credit card payment method in the Shoplus platform. Suitable for merchants who need to integrate international payment solutions, covering major global markets. Key steps include entering payment settings, selecting and activating PingPongPay, entering necessary parameters such as ClientID, AccId and Salt, and enabling - [Xorder&PingPongCheckout Configuration](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/services/buildingTools/xorder/index.md): This document introduces the configuration process for Xorder and PingPongCheckout, including logging into the xorder merchant backend, setting up PingPong payment channels, and specific steps for domestic merchant integration. It is suitable for merchants in China who need to integrate PingPong payment solutions, ensuring smooth completion of payment function configuration and usage. - [Local Payment Support List](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/services/checkout/apm/apmList/index.md): The local payment support list provides various local payment methods in China and South Korea along with their transaction currencies. In China, Alipay and WeChat Pay are supported, covering multiple international currencies; South Korea lists a wide range of bank and credit card options including KBCard, HANACard, etc. This information helps merchants understand and select suitable payment methods to meet the needs of customers in different regions. - [Hosted-Embed Checkout via JS-SDK](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/services/checkout/hosted/sdk/index.md): Embed PingPongCheckout checkout via JS-SDK, suitable for scenarios requiring payment functionality integration in web pages. Supports custom theme colors and multi-language configuration. Main parameters include innerJsUrl and token for loading and initializing the SDK. When creating payment, pass the order object and set mode to sandbox or production. The checkout supports re-payment within 48 hours - [3DS external](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/threeDS/3DSexternal/index.md): The 3DS external API is used for merchants to actively submit 3DS verification result processing flows. It applies to online payment scenarios requiring additional cardholder authentication, supporting major card organizations such as Visa and American Express. Key parameters include executeThreeD (fixed value external), authenticationValue (authentication - [api](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/threeDS/api/index.md): threeDS API Used to collect and submit browser information to enhance payment security. Applicable to online payment scenarios requiring 3D secure authentication. Key parameters include language, screenWidth, javaEnabled, etc. This information helps identify real users and reduce fraud risk. - [avsResult](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/threeDS/avsResult/index.md): The avsResult documentation provides detailed descriptions of AVS verification results and their applications. Applicable to all issuing banks, it offers specific response codes and meanings according to different card schemes (such as Visa, Mastercard, American Express, etc.). For example, A indicates address matches but postal code does not match, N indicates neither address nor postal code matches. - [depends3D](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/threeDS/depends3D/index.md): The depends3D interface is used for PingPongCheckout's 3DS decision process, applicable to end-to-end integration methods. The key parameter `executeThreeD` needs to be set to `depends` to enable 3DS verification. The Checkout JS-SDK already has 3D Secure functionality built-in, no additional integration required. - [Force3D](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/threeDS/Force3D/index.md): Force3D Used to enforce 3DS authentication during the payment process. Suitable for scenarios requiring enhanced transaction security, especially under end-to-end integration methods. When the key parameter `executeThreeD` is set to `Y`, it triggers the forced 3DS verification process. PingPongCheckout's checkout JS-SDK has built-in 3D Secure functionality, no additional integration required. - [riskJs](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/threeDS/riskJs/index.md): The riskJs component is used to integrate 3D Secure verification, suitable for scenarios requiring enhanced online payment security. Key functions include initialization settings and collecting card information for 3D init. Key parameters include env, accId, clientId, etc., supporting card information transmission via cardInfo or cardToken. The component can automatically generate and return jsGeneratedData. - [Create cardToken - Hosted Mode](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/tokenization/hosted/index.md): Create cardToken - Hosted mode is used to securely store credit card information for quick future payments. Suitable for scenarios requiring simplified user payment processes, such as e-commerce websites. Key features include allowing users to check save card information (excluding CVV/CVC/CVN) during first payment, after which the system automatically displays historical card information for selection. Main functions cover client-side order creation, synchronous response, and obtaining token from asynchronous notifications. - [Create cardToken - NonHosted Mode](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/tokenization/nonHosted/index.md): Create cardToken - NonHosted mode is used to generate card tokens in non-hosted environments. Suitable for scenarios that require improved payment security and reduced PCI DSS compliance burden. The main steps include client order placement with specified parameters to request cardToken creation, obtaining the token through API synchronous response and asynchronous notifications. Tokens can be obtained normally after successful payment, but cannot be obtained if payment fails. - [Token Unbinding](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/tokenization/unbind/index.md): Token unbinding function allows merchants to cancel bound payment tokens, making the token invalid but not affecting subsequent operations of previous transactions such as refunds. Called via POST request, requires necessary parameters including clientId, accId and token information to be unbound. Supports sandbox and production environment deployment. - [Non-hosted Debugging Tool](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/tools/api/index.md): The Non-hosted debugging tool is designed specifically for API debugging during the development phase. It supports receiving the bizContent parameter as either a JSON object or string, ensuring developers follow document specifications when passing parameters to verify the correctness of requests and responses. - [Payment Request Tool](https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/tools/request-tool/index.md): The Payment Request Tool is used for quickly debugging payment request parameters and response results. To ensure payment method compatibility, this tool is provided as an independent static page, not embedded via iframe. ## API Specification This section contains machine-readable API specification files for AI tools and developers. - [OpenAPI Specification](https://acquirer-api-docs-v4-en.pingpongx.com/api/openapi.json): Full OpenAPI 3.1.0 specification with definitions, parameters, and response formats for all 36 API endpoints - [API Index](https://acquirer-api-docs-v4-en.pingpongx.com/api/index.json): Endpoint index containing each API name, path, method, and documentation link ### Quick Start ``` # Fetch the OpenAPI specification curl https://acquirer-api-docs-v4-en.pingpongx.com/api/openapi.json # Fetch the API index curl https://acquirer-api-docs-v4-en.pingpongx.com/api/index.json ```