China Merchants Bank's payment Interface

Online Payment Method

Although the consumer sends a notification to the merchant after the payment is successfulLine problem, merchant network configuration change problem, merchant server problem, merchantProgramFor problems and other reasons, the procedure for the merchant to finally receive the notification from the bank may not receive the notification from the bank. Therefore, the merchant cannot determine whether to provide services to consumers simply by receiving the notification from the bank, this factor should also be taken into account when the merchant designs the system. The merchant system must be able to handle repeated notifications.

Prerequisites:
1. The banking system is always correct.
Then, as long as the merchant receives a (legal) notification, such as: after receiving the notification of successful payment, immediately change the status of the order to "paid ".

2. the system stability of the Internet and merchants is untrusted.
Since the links from the bank to the merchant system are the Internet, and the stability of the merchant system is untrusted, we can only eliminate the consequences of instability through "redundancy" (as far as possible: that is, you have not received a notification of successful payment (that's all, because for the merchant, except for the bank prompt that the payment is successful, the payment fails in any case-nonsense ).
If the merchant must use a program to checkout the bank
Program processing logic: If the checked-out order is different from the merchant database, it must be more likely than the merchant (that is, the merchant has not received the notification ), then, perform some automatic correction or explicit reminders. For example, the merchant database prompts the bank to close the order that has been checked out while the merchant database is not checked out, or the merchant administrator: Which tickets have problems.