API Description

1. Communication Protocols

Merchants accessing the PayerMax service and calling the API must follow the following rules:

type	desc
Transmission Method	In order to ensure transaction security, HTTPS transmission is adopted, and TLS version should not be lower than 1.2. For details, please refer to TLS Upgrade Instructions
Submission Method	Submit by POST method
Data Format	Submit and return data in application/json format
Character Encoding	Uniformly use UTF-8 character encoding
Signature Algorithm	SHA256WithRSA
Signature Requirements	Both request and received data need to verify the signature. For details, please refer to Config Settings and Signature Rules
Process Logic	First refer to the return of the protocol field, then refer to the code in the response message, and finally refer to the transaction status

2. API Structure

The following is the HTTP structure of the PayerMax interface, the interface name is placed after the request address, and the content in the data is a packet spliced by different service structures

POST https://pay-gate.payermax.com/aggregate-pay/api/gateway/{Endpoint}
Content-Type: application/json
Content-Length: 580
sign: Use merchant privateKey signatures based on the request body

{
    "version": "1.1",
    "keyVersion": "1",
    "requestTime": "2022-01-17T08:04:13.879+00:00",
    "appId": "3b242b56a8b64274bcc37dac281120e3",
    "merchantNo": "020213827212251",
    "data": {
    }
}

Request Url:

Environment	Link
Test	https://pay-gate-uat.payermax.com/aggregate-pay/api/gateway
Prod	https://pay-gate.payermax.com/aggregate-pay/api/gateway

3. API List

Product	Integration Mode	Interface Name	Endpoint	Description
Receipt	Cashier Payment	Place an Order	/orderAndPay	Use PayerMax cashier for payment
		Transaction Inquiry	/orderQuery
		Order Asynchronous Notification	/notification
		Refund Application	/refund
		Refund Inquiry	/refundQuery
		Refund Asynchronous Notification	/notification
	Pure API Payment	Place an Order	/orderAndPay	Use merchant's own cashier for payment
		Transaction Inquiry	/orderQuery
		Order Asynchronous Notification	/notification
		Refund Application	/refund
		Refund Inquiry	/refundQuery
		Refund Asynchronous Notification	/notification
	Tokenization Payment	PaymentTokenID Inquiry	/inquirePaymentToken	When users use card payment, after a successful payment, the card token will be given to the merchant. Subsequent payments by the merchant will carry the card token for quick payment completion.
		PaymentTokenID Unbinding	/removePaymentToken
		Asynchronous Notification	/notification
	PayByLink Payment	Create Payment Link	/createPaybylink	Directly create a payment link for the merchant, send it to the consumer for payment
		Query Link Details	/queryPaybylink
		Invalid Payment Link	/expirePaybylink
		Update Asynchronous Callback	/notification
	Disputes	Dispute Asynchronous Notification	/notification	Notifications to merchants for orders generated due to chargebacks, disputes, fraud, complaints, etc., after the completion of the transaction
		Case Reply	/caseReplay
		Case Inquiry	/caseSearch
Payment	API Payment	Payment Request	/paymentOrderPay	Merchant makes payment to users
		Payment Transaction Inquiry	/paymentOrderQry
		Asynchronous Notification	/notification
Account Balance	Balance Inquiry	Real-time Balance Inquiry	/currentBalanceQuery	Merchant performs balance inquiry
		Day-end Balance Inquiry	/dayEndBalanceQuery
Payment Method	Payment Method Inquiry	Available payment methods inquiry	/consultPaymentMethod	Merchants can query the currently available payment methods, including: payment method code, payment currency, activation time, payment method status (available/unavailable), limit range, etc.

4. API parameter transfer rules

If required	Description
M	Mandatory
O	Optional
C	Condition