Main Participants

PingPongCheckout's offline card payment solution integration enables communication between SAAS cash registers and POS devices through cloud services to complete payment, query, refund, and other transaction processes. This solution uses REST API methods and ensures transaction requests are accurately routed to designated POS terminals through clear device identification mechanisms.

• SAAS Cash Register: Initiates transaction requests and receives transaction results
• PingPong Acquiring Service: Acts as middleware, handling request routing and response forwarding
• POS Device: Executes actual payment operations and processes card transactions

API List

1. Payment API
2. Single Transaction Query API
3. Refund Application API
4. Refund Query API

Payment Process

Initiate Payment Request

The SAAS cash register sends a unified payment request (unifiedPay) to the PingPong acquiring service The request contains deviceSn and deviceModel parameters to clearly specify the target POS device Also includes cashierDeviceId to identify the cash register itself

Note

The deviceSn, cashierDeviceId, and deviceModel parameters ensure payment requests are correctly routed to the designated POS device. Please ensure parameters are filled correctly, otherwise it may cause payment failure or requests to be routed to the wrong POS device

Request Routing

The PingPong acquiring service receives the request and verifies the signature Routes the payment request to the designated POS device based on deviceSn and deviceModel

Payment Processing

The POS device receives the request and executes the payment operation (such as card swipe, NFC payment, etc.) After processing is complete, the POS device returns the result to the acquiring service

Result Return

The acquiring service returns the payment result to the SAAS cash register. The synchronous response result may be PROCESSING status, and the payment result needs to be obtained through the query API, The SAAS cash register receives the result and performs subsequent processing (such as printing receipts, updating order status, etc.)

Refund Process

Initiate Refund Request

The SAAS cash register sends a refund request (refund) to the acquiring service For POS transaction refunds, deviceSn and deviceModel parameters must be included The request contains original transaction information and refund amount

Refund Routing

The acquiring service verifies the request and routes it to the designated POS device The POS device executes the refund operation

Result Return

The POS device returns the refund result to the acquiring service. The synchronous response result may be PROCESSING status, and the payment result needs to be obtained through the query API, The acquiring service returns the refund acceptance result to the cash register

Previous pageOverview

Next pageQR code payment