ISV Integrations

1. API parameters

The appId of PMMax represents the system-integrated application, and the key is bound to the appId. For the ISV service provider, the system integration is performed by the ISV service provider, so the appId in the transaction interface is the appId of the ISV service provider. The actual business is generated by a specific merchant, so the merchantNo sent is the merchantNo that the merchant signed the business in PMMax and assigned.

Parameter	Type	If Required	Length Max.	Description	Example
version	String	M	8	API version. Current value: 1.1	1.1
keyVersion	String	M	8	Signature Algorithm Version。Current Value：1
requestTime	String	M	32	Request time，Comply with rfc3339 specification, format: yyyy-MM-dd'T'HH:mm:ss.SSSXXX	2022-01-22T10:00:00.500+08:00
appId	String	M	64	Integration App Id of the integrator	46153e2b787241ae8b01857bb087d1bd
spMerchantNo	String	M	15	Merchant ID of the ISV service provider
merchantNo	String	M	15	Merchant Id, the unique identifier generated when the merchant signs the contract with PayerMax	010229810189301
+data	Object			Please refer to the specific fields under each service interface
「+......

2. Authorization relationship

When a merchant initiates a payment transaction through the platform of the ISV service provider, it needs to authorize the appId of the ISV service provider in the background of PMMax. After the authorization is completed, PMMax will allocate an auth token. ISV service providers need to send merchant_auth_token=auth token assigned by authorization in the http header when requesting a transaction