Comparative analysis
Overview
The following table introduces the corresponding scenarios between AlipayCN and Alipay+.
AlipayCN | Alipay+ |
Third-party Merchant QR Code Payment | Merchant-presented Mode Payment - Entry code |
Merchant QR Code Payment | |
Transaction QR Code Payment | Merchant-presented Mode Payment - Order code |
Barcode Payment | User-presented Mode Payment |
Migration considerations
The following introduces the technical solution for migrating from AlipayCN to Alipay+ in different payment scenarios and the API differences.
Third-party Merchant QR Code Payment
The following introduces the differences in routing logic.
Before: The ACQP routes the order to AlipayCN according to AlipayCN's UA. For more information about AlipayCN integration, see Third-party Merchant QR Code Payment.
After: The ACQP routes the order to Alipay+ according to Alipay+ wallet's UA. Alipay+ wallet's UA includes AlipayCN.
After migration, identify Alipay+ wallets according to AlipayCN's UA and Alipay+ wallet's UA.
AlipayCN's UA: AlipayClient
Alipay+ wallet's UA: AlipayConnect
The routing strategy differs according to the wallets, migration progress, merchant's willingness, and Alipay+ services, see the following for details.
Merchant QR Code Payment
The following introduces the differences in obtaining the merchant QR code.
Before: A merchant obtains AlipayCN's static merchant QR code in advance and displays the code for customers to scan and pay. For more information about AlipayCN integration, see Merchant QR Code Payment.
After: Alipay+ does not provide merchant QR codes. Merchant-presented Mode Payment Entry Code is used instead.
Transaction QR Code Payment
The following introduces the differences in obtaining the order code.
Before: The ACQP sends the order to AlipayCN to obtain an order code. For more information about AlipayCN integration, see Transaction QR Code Payment.
After: The ACQP sends the order to Alipay+ to obtain an order code.
No change on the merchant side for this scenario. The ACQP needs to integrate with Alipay+.
Barcode Payment
The following table introduces the processing logic of AlipayCN and Alipay+ for the User-presented Mode Payment scenario.
AlipayCN | Alipay+ |
Identify AlipayCN payment code, and route the transaction to the original channel. Code value regular expression: /^(2[5-9]|30)\d{14,22}$/. The ACQP is directly connected with AlipayCN. If the payment code starts with a number between 25~30, and has a length of 16~24 digits, route the transaction to AlipayCN. For more information about AlipayCN integration, see Barcode Payment. | Identify the 19-digit Alipay+ payment code in priority, and route the transaction to Alipay+. Code value regular expression: /^(2[5-9]|30)9\d{10}6\d{5}$/./^(2[5-9]|30)9\d{10}6\d{5}$/ Backup logic: Route all CGCP codes that the ACQP failed to be identified to Alipay+ for decoding. Code value regular expression: /^(2[5-9]|30)\d{14,22}$/. The newly added CGCP codes with a length of 24 digits should be routed to Alipay+ instead of AlipayCN. |
After the migration, route all codes with a length of 16~24 digits and starting with 25~30 to Alipay+.
Note: The processing for AlipayCN payment code and AlipayHK code cannot be distinguished in the User-presented Mode Payment scenario. Therefore, the migration from AlipayCN to Alipay+ must be complete before starting the transaction with AlipayHK.
After the ACQP completes the migration, migrate the merchants in batches, according to their willingness, integration status, migration schedule, and registration status, so transaction flows directly connected with the AlipayCN channel are migrated to the Alipay+ channel.
For a step-by-step guide on how to complete the migration, see Migrate from AlipayCN to Alipay+.