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】 etc. involve the definition of payment methods, the changes are the same as above
二、API Parameter Logic Change
Collection Service
1. 【 Cashier Payment】
New version API parameter change The online integration has no impact, no need to make any changes, the system will automatically match the parameters to generate orders and bills; When adding a payment method, integrate it according to the latest document,see cashier interface【Cashier Payment-API Integration】
Change content：
- In interface parameters, change the input field paymentMethod to paymentMethodType with the same value logic
Impact statement：
- Payment methods already integrated online have no impact and do not need to be re-integrated
- For new access payment methods, use paymentMethodType to integrate
2.【Direct API】
see【Direct API-API Integration】
Change content：
- The Direct API changes the input parameter paymentMethod to paymentMethodType with the same value logic
Impact statement：
- Payment methods already integrated online have no impact and do not need to be re-integrated
- For new access payment methods, use paymentMethodType to integrate
3.【Result Notifications】
Change content：
- The notification parameter paymentMethodType is added, and the paymentMethod parameter is retained, with the same logic for both values
Impact statement：
- For payment methods that have been integrated online, the paymentMethodType parameter is added to the notification parameter, while the paymentMethod is retained, and the value logic is the same for both
- When a new payment method is added, the paymentMethodType parameter is added to the notification parameter, and the paymentMethod parameter is no longer returned
- The check method remains the same
4.【 Transaction Inquiry】
Change content：
- The paymentMethodType is used in the query response parameter instead of the paymentMethod, which takes the same value logically
Impact statemen：
- For payment methods that have been integrated online, the query response parameter adds the paymentMethodType parameter while retaining the paymentMethod, which takes the same value logically
- When a new payment method is added, the paymentMethodType parameter is added to the query response parameter, and the paymentMethod parameter is not returned
- The check method remains the same
Disbursement Service
Change content：
- In interface parameters, change the input field paymentMethod to paymentMethodType with the same value logic
Impact statemen：
- Online integrated payment methods have no impact and do not need to be re-integrated;
- For new access payment methods, use paymentMethodType
三、Statement of change
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) : 【Payment Method Mapping】
For examples before and after the bill header change, please refer to: 【Payin Report】、 【Payout Report】、 【Bill Report】、 【Settle Details】、 【Sum Settled】