Background：

At present, the rules of different countries are inconsistent in the naming of the first and second tiers of global payment methods in PayerMax business, and there will be differences in the naming of the same type of payment methods in the external quotation of commerce, resulting in relatively high understanding costs for merchants in the process of reconciliation, data processing and payment docking. In the following case, before optimization, the names of Credit cards in different countries will appear at the same time: Debit/Credit Card, Visa/MasterCard, or directly named Card; Wallet may also exist E-wallet, Mobile Wallet, or directly named Wallet, but the same type is named differently; This time, to solve the above problems, the global payment method unified management, internal and external unified naming, synchronous modification of the billing logic, payment method field from the history of 2 fields, expanded to 3 fields, complete the optimization of the bill, convenient for merchants to reconcile and data analysis.

Post-iteration advantage：

• The name of the payment method product and the bill is unified, and the reconciliation is clearer
• The naming of global payment methods is unified, the definition of payment method types is revised, the management of payment methods and target institutions is refined, the logical definition is clear, and data analysis and processing are more convenient

一、 Merchant side changes：

MMC Merchant Platform

The naming information of the global payment method is unified, and the following three fields are changed in the drop-down box, details page, and export bill of each module. The details are as follows:

1.【 Settings 】-【 Profile】-【 Contract info 】- Name of payment method change description：

• The original payment method display and interface parameter transmission/contract contract payment method may be inconsistent, but after optimization, it is changed to be consistent with the contract product
• Adjust the part payment name, such as the Debit/Credit Card) is adjusted for the Visa/Master Card 】, for a complete list please refer to：【Old and New Version Payment Method Mapping】

History Display： New Display：

2.【 Payment】-【 Order search】-【 Payment Method 】- Drop down box/list display change description：

• The payment method drop-down box displays the same as the contract name

History Display： New Display：

3. 【 Payment】-【 Order search】-【 Order details 】- Details displaychange description：

The definition logic of the original first-level payment method and second-level payment method may be inconsistent with the contract. After optimization, the expression of first-level and second-level payment method is no longer used. Add the following:

• 【Payment Method Type】, consistent with interface parameter passing paymentMethodType
• 【Payment Method】, consistent with the contract products
• Target organization /Card group 【Target Org/Card Org】, consistent with the interface parameter targetOrg/cardOrg

History Display： New Display：

Other sync pages involving payment methods such as: 【 Payment】、【Disbursement】、【Chargeback】、【 Subscription】 etc. involve the definition of payment methods, the changes are the same as above

二、API Parameter Logic Change

【Collection Service 】

1. 【API】

The online integration has no impact, no need to make any changes, the system will automatically match the parameters to generate orders and bills; if the integrated merchant needs to connect to a new payment method, then follow the latest official website documents to transfer parameters，see【Payment Request-API Checkout】

Change content：

• The input parameter removes the paymentType parameter
• Input parameter New fields：paymentMethodType、targetOrg、cardOrg

Impact statement：

• Online integrated payment methods have no impact and do not need to be re-integrated
• New access mode of payment, please use the paymentMethodType integration, targetOrg, cardOrg, please refer to the new and old payment mapping,see：【Payment Method Mapping】

2.【Order Query Results】

see【Result Query】

Change content：

• The version of the interface was upgraded. The version parameter was 2.7
• New fields in response parameters：paymentMethodType、targetOrg、cardInfo.cardOrg
• The paymentType parameter is no longer returned. For the mapping relationship between paymentType and paymentMethodType, targetOrg, and cardOrg, please refer to:【Payment Method Mapping】

Impact statement：

• The online integrated payment method has no impact and does not need to be reintegrated. If you need to return new parameters and invoke the order query API interface, change version to 2.7
• With the newly integrated payment method, all fields in the official website will be returned when version field pass 2.7 is requested
• Visa inspection method

3.【Asynchronous callback notifications】

see【Notification Callback】

Change content：

• Added parameters to the notification parameters: paymentMethodType, targetOrg, cardInfo fields, where cardInfo is of String type and in json format:

{
  "cardIdentifierName":"*D",
  "cardIdentifierNo":"520000******0007",
  "cardOrg":"MASTERCARD"
}

Impact statement:

• If merchants need new notification parameters, they need to contact our technical support to upgrade the notification version. After the upgrade, paymentType parameter is no longer returned, and parameters such as paymentMethodType, targetOrg, cardInfo and so on are added
• PaymentType the mapping relationship with paymentMethodType, targetOrg, cardOrg, please refer to:【Payment Method Mapping】
• Visa inspection method

【Disbursement Service】

see【API Disbursement】

Change content:

• Remove the payType parameter from the input parameter
• Input parameter new fields: paymentMethodType, targetOrg

Impact statement：

• Online integrated payment methods have no impact and do not need to be re-integrated
• For new access payment methods, use paymentMethodType and targetOrg for integration, see

【Payment Method Type and Target Org】
【Payment Method Mapping-Payout】

For payment methods that have been integrated in the old version, you still need to use the payout fields of the old version. Please continue to refer to the following payment application template：Disbursement Application Template and Filling Instructions

三、Change of Statement

Delete two fields: Payment Method, Sub Payment Method

Add three new fields, display form:

Payment Method Type	Payment Method	Traget Org/Card Org
CARD	VISA/MASTER	VISA
WALLET	DANA	DANA

• 【Payment Method Type】，consistent with interface parameter passing paymentMethodType
• 【Payment Method】，onsistent with the contract products, easy to check the execution rate
• 【Target Org/Card Org】，consistent with the interface parameter targetOrg/cardOrg;

For the mapping between deleted fields and new fields, see (Only the changed part is displayed) :

Collection：【New and Old Mapping-Collection】 Disbursement：【New and Old Mapping-Disbursement】

For examples before and after the bill header change, please refer to: 【Payin Report】
【Payout Report】
【Bill Report】
【Settle Details】
【Sum Settled】