# Release Notes > **Note:** With the introduction of Push Mode to Merchant-presented Mode Payment in [Version 1.4.0](#TdbcI), the mode described in previous versions is now referred to as Pull Mode. For the definitions of the two modes, see [Basic concepts of Merchant-presented Mode Payment](../product_intro_acq/product_mpm_acq#e3fx5). ## Version 1.6.1 Release date: 2026/04/27 ### Document improvements - Removed the following optional parameters from the [pay (User-presented Mode Payment)](../api_acq_tile/pay_user_presented_mode), [pay (Merchant-presented Mode Payment - Entry Code)](../api_acq_tile/pay_entry_code), [pay (Merchant-presented Mode Payment - Order Code)](../api_acq_tile/pay_order_code), [pay (Cashier Payment)](../api_acq_tile/pay_cashier), [pay (Auto Debit)](../api_acq_tile/pay_auto_debit), [userInitiatedPay (Merchant-presented Mode Payment - Private Order Code)](../api_acq_tile/pay_private_order_code), and [consultPayment](../api_acq_tile/consult_payment) APIs: - _order.env.cookieId_ - _order.env.clientIp_ - _order.env.deviceTokenId_ - _order.env.storeTerminalRequestTime_ - _order.env.storeTerminalId_ - Removed the following optional parameters from the [prepare](../api_acq_tile/prepare) API: - _useragent_ - _osVersion_ ## Version 1.6.0 Release date: 2026/02/28 ### New features - Added the _order.indirectAcquirer_ parameter to the following APIs: - [pay (User-presented Mode Payment)](../api_acq_tile/pay_user_presented_mode) - [pay (Merchant-presented Mode Payment - Entry Code)](../api_acq_tile/pay_entry_code) - [pay (Merchant-presented Mode Payment - Order Code)](../api_acq_tile/pay_order_code) - [userInitiatedPay (Merchant-presented Mode Payment - Private Order Code)](../api_acq_tile/pay_private_order_code) ### Document improvements - Replaced the complex routing logic section with guidance to contact Alipay+ Solution Architect when the routing logic in a merchant payment code conflicts with Alipay+ code routing logic. See the [Accept a payment](../integration_user_mode_acq/accept_payment) topic in the User-presented Mode Payment scenario for details. - Refined the description of using the prepare API when binding the user account in the Auto Debit scenario. See the [Bind the user account](../integration_auto_debit_acq_tile/bind_user_account) topic for details. ## Version 1.5.0 Release date: 2026/02/25 ### New features - Added distinct requirements for payment networks and acquiring institutions implementing Push Mode. For more information, contact your Alipay+ Solution Architect. ## Version 1.4.10 Release date: 2025/12/31 ### Document improvements - Removed the **show child parameters** menu for parameters without child parameters in the API reference. ## Version 1.4.8 Release date: 2025/08/29 ### New Features - Added iScan and Auto Diagnosis tools in Alipay+ Developer Center for ACQPs. ## Version 1.4.7 Release date: 2025/06/30 ### Document improvements - Fixed broken links. ## Version 1.4.6 Release date: 2025/04/30 ### Document improvements - Fixed broken links. ## Version 1.4.5 Release date: 2025/02/28 ### Document improvements - Added a private key example to the _Sign a request_ section, added an Alipay+ public key example to the _Handle a response_ section, and updated the example explanations in the _Send a response_ section in [Sign a request and validate the signature](../api_acq_unified/signature). ## Version 1.4.4 Release date: 2024/12/31 ### Document improvements - Added notes to explain that Participant ID and _participantId_ refer to Partner ID. - Updated the further action for the error code INVALID\_TOKEN to instruct the ACQP to disable the user's Auto Debit immediately. For more information, see [**pay (Auto Debit)**](../api_acq/pay_auto_debit). ## Version 1.4.3 Release date: 2024/10/31 ### Document improvements - Refined the workflow diagrams and integration steps for the [entry code](../integration_merchant_mode_acq/accept_payment_entry_code), [order code](../integration_merchant_mode_acq/accept_payment_order_code), and [private order code](../integration_merchant_mode_acq/accept_payment_private_order_code) scenarios of Merchant-presented Mode Payment. - Added precision and length requirements for the _quotePrice_ parameter in the [**pay (User-presented Mode Payment)**](../api_acq/pay_user_presented_mode), [**pay (Auto Debit)**](../api_acq/pay_auto_debit), [**refund**](../api_acq/refund), [**notifyPayment**](../api_acq/notify_payment), and [**inquiryPayment**](../api_acq/inquiry_payment) APIs. - Clarified that the request parameter order.merchant.store is required in the following pay APIs for the in-store payment scenarios: - [**pay (User-presented Mode Payment)**](../api_acq/pay_user_presented_mode) - [**pay (Merchant-presented Mode Payment - Entry Code)**](../api_acq/pay_entry_code) - [**pay (Merchant-presented Mode Payment - Order Code)**](../api_acq/pay_order_code) - [**userInitiatedPay (Merchant-presented Mode Payment - Private Order Code)**](../api_acq/pay_private_order_code) - Updated the description for Object Identification Number. For more information, see [Code Format Specification-Collection code](../code_scanning_payment_standards_acq/code_format#Tr6Vv). - Optimized the [Partner services FAQ](../faq_acq/partner_services) section in the following aspects: - Added several FAQs. - Removed outdated FAQs. - Updated and refined answers to some FAQs. - Added a navigation menu on each page to facilitate easy access to specific FAQs. ## Version 1.4.2 Release date: 2024/08/30 ### Document improvements - Updated the Alipay+ Brand Mark Assets and refreshed the user experience images with the latest Alipay+ logo. To download the assets and ensure your branding is current, visit [Alipay+ Brand Mark Assets](../brand_guidelines_acq/brand_assets) and [Product Introduction](https://docs.alipayplus.com/alipayplus/acqp_payment_product_overview_1.4.2). - Fixed some minor errors in the [reconciliation reports' naming convention descriptions](../reconcile_acq/trans_detail). ## Version 1.4.1 Release date: 2024/06/28 ### Document improvements - Added the following risk management FAQs: - [What should I do to become an Alipay+ Partner?](../faq_acq/risk_management#AZGh2) - [What are the payment risk management requirements for an Acquiring Partner?](../faq_acq/risk_management#sSDZb) - [What are the prohibited sales requirements for an Acquiring Partner?](../faq_acq/risk_management#Y3NXG) - Optimized the [Integration and acceptance FAQ](../faq_acq/integration) section in the following aspects: - Removed outdated FAQs. - Updated and refined answers to some FAQs. - Added a navigation menu on each page to facilitate easy access to specific FAQs. ## Version 1.4.0 Release date: 2024/04/30 ### New features - Added Push Mode to Merchant-presented Mode Payment. In this mode, the MPP makes the payment, which is then pushed by Alipay+ to the ACQP. The ACQP completes the transaction by accepting the payment. For more information about Push Mode, contact the Alipay+ Solution Architect. ### Document improvements - Added release notes for Alipay+ ACQP Android SDK and Alipay+ ACQP iOS SDK. For more information, see the following documents: - [Release notes for Alipay+ Android SDK](../sdk_acq/release_note_android) - [Release notes for Alipay+ iOS SDK](../sdk_acq/release_note_ios) ## Version 1.3.5 Release date: 2024/02/29 ### Document improvements - Deleted the misrepresentation that ECC256 is a supported signature algorithm in constructing API request headers and API response headers, retaining the RSA256 algorithm, which refers to SHA256withRSA. For more information, see [API Reference](../api_mpp/api_overview). - Corrected the description of the SDK method to consult the Alipay+ payment method information in the [Cashier Payment](../integration_cashier_acq/accept_payment#FfiOo) and [Auto Debit](../integration_auto_debit_acq/account_binding#vG31K) integration guides. - Added an FAQ about [how to troubleshoot an invalid signature issue](../faq_acq/integration#Nao1l). - Added an FAQ specifying the usage of the API endpoint in both the production and sandbox environments. For more information, see [Integration](../faq_acq/integration#C6rl9). - Added an FAQ about the refund scenario when a merchant's account has insufficient funds. For more information, see [Migration from AlipayCN or AMS](../faq_acq/migration). ## Version 1.3.4 Release date: 2023/12/29 ### Document improvements - Updated the _referenceOrderId_ parameter in the [**declare**](../api_acq/declare) and [**inquireDeclarationRequests**](../api_acq/inquire_declaration_status) APIs from `Optional` to `Required`. - Added the _Agent-Token_ parameter into the request structure figure in the API Reference. For more information, see [Request structure](../api_acq/api_overview#DSjrC). ## Version 1.3.3 Release date: 2023/10/31 ### Enhanced features - Changed the e-mail address for Alipay+'s after-sales service from connect\_support@service.alipay.com to overseas\_support@service.alibaba.com. ### Document improvements - Added a note that all amount values in the reconciliation reports are provided in the smallest unit of the corresponding currency without decimal places. For more information, see [Reports and reconciliation tasks](../reconcile_acq/reconcile_overview#b7GmN). - Added the information that Alipay+ does not retry to send the notification if you test Alipay+ APIs in the sandbox environment. For more information, see [Retry mechanism](../integration_auto_debit_acq/handle_notification#sFs5z). - Removed the incorrect description from the [**refund**](../api_acq/refund) API specification that partial refunds are not allowed for IDR. ## Version 1.3.2 Release date: 2023/08/31 ### Enhanced features - Added the sandbox report directories to the [Download reports](../reconcile_acq/download_report) chapter in _Reconcile_. - Updated the official acceptance mark of Alipay+ in [Brand Display Guidelines for In-store Payment](../brand_guidelines_acq/brand_in_store_acq). ### Document improvements - Corrected the regular expression of an Alipay+ 19-digit code to `/^289\d{10}6\d{5}$/`, which is used in the payment code identification for payment routing in the User-presented Mode Payment scenario. See [Routing logic](../integration_user_mode_acq/accept_payment#Nlj2z) for details. - Added a condition under which the _env.osType_ parameter must be specified when the ACQP calls the [**pay (Merchant-presented Mode Payment -Entry Code)**](../api_acq/pay_entry_code) API. - Removed the value `U` from the value list of the _paymentResult.resultStatus_ parameter in the [notifyPayment](../api_acq/notify_payment) API. ## Version 1.3.1 Release date: 2023/06/30 ### Document improvements - Updated the page designs that are supported by the MPP in the User-presented Mode Payment scenario. For more information, see the [_User experience_](../product_intro_acq/product_upm_acq) section of _User-presented Mode Payment_ _production introduction_. - Updated the page designs that are supported by the MPP in the Merchant-presented Mode Payment scenario. For more information, see the [_User experience_](../product_intro_acq/product_mpm_acq) section of _Merchant-presented Mode Payment_ _production introduction_. - Refined the content structure of the [_Migration guide for AlipayCN to Alipay+_](../migrate_alipaycn_aps/) to make it easy to use. - Corrected the field name _feeSettleAmountValue_ to _feeSettlementAmountValue_ in the sample fee reports of the [_Fee Report_](../reconcile_acq/fee) topic. ## Version 1.3.0 Release date: 2023/04/28 ### New features - Added the `USER_NOT_EXIST` result code for the [refund](../api_acq/refund) API. ### Enhanced features - Optimized the user experience when Alipay is selected to make payments in the Cashier Payment scenario. To enable the optimization, changed the maximum length of the _normalUrl_ parameter in the [pay (Cashier Payment)](../api_acq/pay_cashier) API from 2048 to 4096 characters and added the [canProcessOrderWithPaymentResult](../sdk_acq/ios_canprocessorder) and [processOrderWithPaymentResult](../sdk_acq/ios_processorder) APIs to the iOS SDK. For more information, see the following topics: - [Cashier Payment user experience](../product_intro_acq/product_cashier_acq#O9JWp) - [Accept a payment](../integration_cashier_acq/accept_payment) - [iOS SDK reference](../sdk_acq/ios_quick) - [Android SDK reference](../sdk_acq/android_quick) - Updated the types of Alipay+ payment codes used in the User-presented Mode Payment scenario. For more information, see [Code types and rules](../integration_user_mode_acq/payment_codes). ### Document improvements - Updated the [Idempotency](../api_acq/idempotency) topic in the _API reference_ to include key parameters that are checked for consistency in idempotency control. - Added the [Timeout](../api_acq/timeout) topic to the _API reference_ to introduce the timeout values set by Alipay+ for each API request and how to set the timeout value when calling Alipay+. ## Version 1.2.6 Release date: 2023/02/28 ### Enhanced features - Modified the maximum length of the following parameters from 64 characters to 32 characters: - the _merchantInfo.referenceMerchantId_ parameter in the [registration](../api_acq/registration) API - the _referenceMerchantId_ parameter in the [inquiryRegistrationStatus](../api_acq/inquiry_registration_status) and [notifyRegistrationStatus](../api_acq/notify_registration_status) APIs - the _order.merchant.store.referenceStoreId_ parameter in the [pay (User-presented Mode Payment)](../api_acq/pay_user_presented_mode) and [pay (Merchant-presented Mode Payment - Entry Code)](../api_acq/pay_entry_code) APIs. - Shortened the minimum waiting time for updating an existing registration from 7 natural days to 30 minutes since the last registration request, and removed the prohibition on updating an existing registration that is not processed. For more information, see the [registration](../api_acq/registration) API specification. - Updated the design of the **Alipay+ Checkout Page** in the Cashier Payment - Web scenario. For more information, see the [User experience](../product_intro_acq/product_cashier_acq#X7wg0) section of _Cashier Payment_ _production introduction_. - Updated the User Agent string that is used to identify the KaKao Pay wallet in the Merchant-presented Mode Payment Entry Code scenario. For more information, see [Identify the wallet and route the payment](../integration_merchant_mode_acq/accept_payment_entry_code#ZBmuL) and [mapping table](../integration_merchant_mode_acq/accept_payment_entry_code#ZXlxm). ### Document improvements - Updated the description of the _authClientId_ parameter in the [cancelToken](../api_acq/cancel_token) and [authNotify](../api_acq/auth_notify) API specifications, stating that the value of the _authClientId_ parameter must be consistent with the one in the [prepare](../api_acq/prepare) API. - Added a note to emphasize that the _paymentNotifyUrl_ parameter in the **pay** APIs must be an HTTPS URL. For more information, see the following API specifications: - [pay (User-presented Mode Payment)](../api_acq/pay_user_presented_mode) - [pay (Merchant-presented Mode Payment - Entry Code)](../api_acq/pay_entry_code) - [pay (Merchant-presented Mode Payment - Order Code)](../api_acq/pay_order_code) - [pay (Cashier Payment)](../api_acq/pay_cashier) - [pay (Auto Debit)](../api_acq/pay_auto_debit) - Added a note to emphasize that the _paymentRedirectUrl_ parameter in the **pay** APIs must be an HTTPS URL or in the form of a URL scheme. For more information, see the following API specifications: - [pay (User-presented Mode Payment)](../api_acq/pay_user_presented_mode) - [pay (Merchant-presented Mode Payment - Entry Code)](../api_acq/pay_entry_code) - [pay (Merchant-presented Mode Payment - Order Code)](../api_acq/pay_order_code) - [pay (Cashier Payment)](../api_acq/pay_cashier) - Corrected the name of the logging API provided by Alipay+ iOS SDK from **log** to **logWithName** in the _iOS SDK reference_. For more information, see [iOS SDK Overview](../sdk_acq/ios_overview). - Added a note in the _Reconcile_ documentation to emphasize that Alipay+ reports prevail when discrepancies exist due to payment status inconsistencies between the ACQP system and the Alipay+ system. For more information, see [Process overview](../reconcile_acq/how_to_reconcile#YN0ye) of the _Perform reconciliation_ topic. ## Version 1.2.5 Release date: 2022/12/30 ### New features - Provide accelerated domain names to enable faster access to Alipay+ APIs. For more information, see [Environment](../api_acq/api_overview#bfZS0). ### Enhanced features - Added a note that the ACQP needs to ensure that the amounts in IDR are not in cents. For more information, see the note added to the _paymentAmount.value_, _refundAmount.value, and transactionReceipt.orderAmount.value_ parameters in the API reference documentation. - Removed the value `OTHER` from the _osType_ parameter in the [prepare](../api_acq/prepare) API. - Removed the enumeration value `MINI_APP` from the _terminalType_ parameter in the [prepare](../api_acq/prepare) API specification because currently authorization cannot be initiated via mini apps. - The value of the _authClientId_ parameter in the [applyToken](../api_acq/apply_token) API must be the same as the one specified in the [prepare](../api_acq/prepare) API. - Defined the maximum length of the _declarationRequestsNotFound_ parameter as 64 characters in the [inquireDeclarationRequests](../api_acq/inquire_declaration_status) API. ### Document improvements - Released a series of video tutorials on Alipay+ integration and partner services to enrich your information experience. To watch these videos, see [Videos](https://docs.alipayplus.com/alipayplus/acqp_videos.md). - Added a quick start for Cashier Payment to help the ACQPs quickly build a smooth Cashier Payment process with the Alipay+ Unified Payment solution. For more information, see [Quick start](../integration_cashier_acq/quick_start). - Added an introduction about the Alipay+ customs declaration product. For more information, see [Customs Declaration](../customs_declaration_acq). - Removed the Older Edition documentation. Instead, the Older Edition documentation is released as [Version 1.0.5](https://docs.alipayplus.com/alipayplus/acqp_payment_tools_overview_1.0.5?role=ACQP&product=Payment1&version=1.0.5). - Removed the MPP brand name table in [Brand Display Guidelines for Cashier Payment](../brand_guidelines_acq/brand_cashier_acq). For the latest MPP brand names, see the topic [Brand names of Mobile Payment Providers](../brand_guidelines_acq/mpp_brand_names). - Reorganized the information architecture of [SDK reference](../sdk_acq) documentation to make it easy to use. - Updated the integration guide for [User-presented Mode Payment](../integration_user_mode_acq) as follows: Removed the Mapping between MPP and routing number table in the original Alipay+ payment codes chapter, and changed the chapter name to [Code rules and types](../integration_user_mode_acq/payment_codes). - Updated the Reconcile documentation as follows: - Added an introduction about Banker's rounding. For more information, see [Banker's rounding](../reconcile_acq/bank_rounding). - Improved the description of the _settlementAmountValue_ parameter and the _feeSettlementAmountValue_ parameter to clarify how they are calculated. ## Version 1.2.4 Release date: 2022/10/28 ### New features Added the _mppPaymentId_ parameter in the following API specifications: - [pay (Auto Debit)](../api_acq/pay_auto_debit) - [pay (User-presented Mode Payment)](../api_acq/pay_user_presented_mode) - [inquiryPayment](../api_acq/inquiry_payment) - [notifyPayment](../api_acq/notify_payment) ### Enhanced features - Updated [Brand Display Guidelines for Cashier Payment](../brand_guidelines_acq/brand_cashier_acq) as follows: - Removed the option to display the standalone Alipay+ logo on the merchant's cashier page. Now an aggregated acceptance mark is required. - Added a new Acceptance mark generator that can be used to generate Alipay+ aggregated acceptance marks. ### Document improvements - Updated the definition of the following terms: Acquiring Service Provider (ACQP), Mobile Payment Provider (MPP), and Common Business Day. For more information, see [Glossary](../glossary/v1). - Added a note to clarify the different _acquirerId_ used when constructing the CDN URL for consulting payment method information in the production and sandbox environment. For more information, see [Cashier Payment](../integration_cashier_acq/cdn_json) and [Auto Debit](../integration_auto_debit_acq/cdn_json) integration guides. - Improved the description about the redirection from the MPP side to the ACQP side in the Cashier Payment scenario. For more information, see [Cashier Payment](../integration_cashier_acq/accept_payment#0NUiP) integration guide and the description of the _paymentRedirectUrl_ parameter in the [pay(Cashier Payment)](../api_acq/pay_cashier) API specification. - Added a note to the [applyToken](../api_acq/apply_token) API specification that specifies the effective period of long-term access tokens must be at least 10 years. - Added the image size of the QR code that is returned by Alipay+ in the Merchant-presented Mode Payment scenario. For more information, see the description of the _displayType_ parameter in the [pay (Merchant-presented Mode Payment - Order Code)](../api_acq/pay_order_code) API specification. - Added a chapter to guide the ACQP to go through tasks before, during, and after UAT. For more information, see [UAT checklist](../get_started_acq/uat_checklist). - Added the _rejectionReason_ parameter to the [notifyRegistrationStatus](../api_acq/notify_registration_status) API specification. ## Version 1.2.3 Release date: 2022/09/30 ### New features - Added a new domain name (https://open-na.alipayplus.com) for Alipay+ APIs. Now there are two domain names for you to select. For more information, see [API reference](../api_acq/api_overview#bfZS0). ### Document improvements - Released the [MPP capabilities](../mpp_list/mpp_capabilities) document to introduce the different capabilities supported by various MPPs. - Updated the [Upgrade from Cashier Payment tile mode](../upgrade_guide_acq/upgrade_from_tile) document to introduce how to display the Alipay+ unified payment method along with other Alipay+ payment methods in a list. - Updated the description of the _order.merchant.merchantAddress_ parameter to include the following content: The value of this parameter is used by Alipay+ to determine whether the transaction is domestic or cross-border and therefore affects the fee calculation logic. - Changed the _paymentNotifyUrl_ parameter in the **pay (Auto Debit)** and **pay (User-presented Mode Payment)** APIs from Required to Optional. - Changed the maximum length of the _merchant.merchantMCC_ and _store.storeMCC_ parameters from 32 to 4 in the following pay API specifications: - pay (Cashier Payment) - pay (Auto Debit) - pay (User-presented Mode Payment) - pay (Merchant-presented Mode Payment - Entry Code) - pay (Merchant-presented Mode Payment - Order Code) - userInitiatedPay - Changed the _settlementStrategy.settlementCurrency_ parameter from Optional to Required in the following API specifications: - pay (Cashier Payment) - pay (Auto Debit) - pay (User-presented Mode Payment) - pay (Merchant-presented Mode Payment - Entry Code) - pay (Merchant-presented Mode Payment - Order Code) - userInitiatedPay - Updated the integration guides of the following payment products: - [Merchant-presented Mode Payment](../integration_merchant_mode_acq) - For the entry code scenario, clarified the payment routing logic and updated the mapping between MPPs and their UA strings. - For the order code and private order code scenarios, refined the workflow diagrams and integration steps. - [User-presented Mode Payment](../integration_user_mode_acq) - Added the Alipay+ Payment Codes chapter to better explain the routing logic in [Accept a payment](../integration_user_mode_acq/accept_payment). - Updated the workflow diagrams and processing logic of integrating the **pay** API. ## Version 1.2.2 Release date: 2022/08/31 ### New features - Added support for Cashier Payment with mini programs. You can now accept a payment with a merchant mini program that is deployed in the mobile apps of Alipay+'s MPPs. For the step-by-step guide for integration and the differences when accepting payments with mini-programs in comparison with other merchant platforms (App, Web, or WAP), see [Accept payments with Mini Program](../integration_cashier_acq/cashier_with_mini_program). - Added support for CDN-based consultation methods in the sandbox environment. For the CDN URL formats used in the sandbox environment, see [Cashier Payment](../integration_cashier_acq/cdn_json) and [Auto Debit](../integration_auto_debit_acq/cdn_json) integration guides. ### Enhanced features - Added a requirement on how to use the registration API in TSP mode: For each merchant, the ACQP needs to provide each TSP with a unique value of the _merchantInfo.referenceMerchantId_ parameter. For more information, see any of the following documents: - [Integration Guides for TSP Mode](../integration_tsp) - [Registration](../registration_acq) - [API reference](../api_acq/registration) ### Document improvements - Removed the SDK download addresses from the SDK reference documentation. You can log on to [Alipay+ Developer Center](https://developers.alipayplus.com/open/console/developer/app/list) to download SDK packages. - Removed the following parameters from the API reference. Note that this change is backward compatible. - From the request parameters of the **pay** API for User-presented Mode Payment, Merchant-presented Mode Payment, Cashier Payment, and Auto Debit: - _paymentMethod.customerId_ - _order.goods.goodsBrand_ - _order.merchant.store.storeOperatorId_ - _order.merchant.store.storePhoneNo_ - From the response parameters of the [userInitiatedPay](../api_acq/pay_private_order_code) API: - _order.goods.goodsBrand_ - _order.merchant.store.storeOperatorId_ - _order.merchant.store.storePhoneNo_ - From the response parameters of the [prepare](../api_acq/prepare) API: - _acquirerId_ - _pspId_ - Added a Notes on result code section in the [API reference](../api_acq) documentation for all the pay APIs to explain the logic of the `ORDER_IS_CLOSED` result code. - Released the following documents to provide guidance on migration to the Alipay+ Unified Payment solutions: - [Migration guide for AlipayCN to Alipay+](../migrate_alipaycn_aps) - [Migration guide for AMS to Alipay+](../migrate_ams_aps) - Updated frequently asked questions about Alipay+ risk management, integration and acceptance, and partner services. For more information, see [FAQ](../faq_acq). ## Version 1.2.1 Release date: 2022/08/05 ### New features - Updated the CDN URL formats for CDN-based consultation methods in the [Cashier Payment](../integration_cashier_acq/cdn_json) and [Auto Debit](../integration_auto_debit_acq/cdn_json) integration guides. - Updated the Android SDK and iOS SDK packages for CDN-based consultation methods in [Android](../sdk_acq/android_integration) and [iOS](../sdk_acq/ios_integration) integration guides. - Removed the _allowedPspRegions_ parameter from the specification of the [pay (Cashier Payment)](../api_acq/pay_cashier) API. - Updated the valid values of the _walletForAccountBinding.walletName_ parameter in the specifications of the [applyToken](../api_acq/apply_token) and [authNotify](../api_acq/auth_notify) APIs. ### Enhanced features Added the _registrationResult.rejectionReason_ parameter to the [inquiryRegistrationStatus](../api_acq/inquiry_registration_status) and [notifyRegistrationStatus](../api_acq/notify_registration_status) APIs. ### Document improvements - Improved the description of the _registrationNo_ parameter in the [registration](../api_acq/registration) API. ## Version 1.2.0 Release date: 2022/07/29 > **Important**: > > Since 2022/07/29, the Alipay+ Document Center has been restructured to provide you with a better user information experience in the following terms: > > - **Centralized content reading**: You can select the role and the product that you want to explore to enter a dedicated content domain. > - **Better navigation experience**: Horizontal tab navigation plus vertical navigation allows you to find the information more easily and quickly; the aggregated overview page for each tab guides you through the important content that Alipay+ provides to you; quick entry provided for you to arrive at the API and SDK reference in one step. > - **Public technical content informatio**n: Since this version, most of the documentation on the Alipay+ Documentation Center has been disclosed to all users except for the following three books: > > - Rules > - Operation guides > - Alipay+ Partner Workspace User Guide > > - **Standardized version control**: Alipay+ supports you in switching the version as you require. > - **Optimized content structure**: The content structure of the integration guides is restructured to allow you to find the product introduction, and the content about reconciliation and merchant registration more conveniently. In addition, the product introduction and the integration guides for the Online Payment are also refined to improve the content quality. > - **Useful support information**: Find the support information at the footer if you need any help with technical issues or business operations. ### New features - Released the Alipay+ Unified Payment edition of Auto Debit. For more information, see [Product introduction](../product_intro_acq/product_debit_acq) and [Integration overview](../integration_auto_debit_acq/integration). Accordingly released the [Brand Display Guidelines for Auto Debit](../brand_guidelines_acq/brand_auto_debit_acq), which replaces the UX design guideline for Auto Debit. - The following parameter changes are applied to the Alipay+ Unified Payment edition of Auto Debit: - In the [pay (Auto Debit)](../api_acq/pay_auto_debit) API specification, the _paymentFactor.presentmentMode_ parameter is changed to **Required** and must be set to `UNIFIED`. - In the [prepare](../api_acq/prepare) API specification, - added the following request parameters: _paymentAmount_, _settlementStrategy_, _userRegion_, and _boundWalletNames_. - removed the following response parameters: _schemeUrl_, _applinkUrl_, and _appIdentifier_. - In the [applyToken](../api_acq/apply_token) API specification, removed the _customerBelongsTo_ request parameter and added the _walletForAccountBinding_ response parameter. - In the [authNotify](../api_acq/auth_notify) API specification, added the _walletForAccountBinding_ request parameter. - Released two CDN-based methods for consulting the Alipay+ payment method information in Cashier Payment and Auto Debit scenarios. The new methods enable the ACQP/merchant to directly request JSON data or logo assets from the Alipay+ CDN server with the following benefits: - less integration cost, higher response speed, and better information transparency - streamlined integration experience and better real-time performance For more information, see the topic _How to consult the payment method information_ in the [Cashier Payment](../integration_cashier_acq/consult_info) and [Auto Debit](../integration_auto_debit_acq/consult_info) integration guides. > **Note**: > > Alipay+ continues to maintain the **consultPayment** API to provide service consistency. ACQPs that have integrated the **consultPayment** API are not impacted. For how to consult Alipay+ payment method information by using the **consultPayment** API, see [consultPayment integration](../acq_ns). - Added the settlement message function for ACQPs. For how to enable this function to receive a message that is attached to each Alipay+ settlement, see [Receive settlement message](../reconcile_acq/reconcile_overview#RGHih) in the _Reconcile_ section. ### Other document improvements - Updated the valid values of the _transactionType_ parameter in the **inquiryPayment** API. - Added a form for submitting custom logo requirements in [Brand Display Guidelines for Cashier Payment](../brand_guidelines_acq/brand_cashier_acq). ## Version 1.1.0 Release date: 2022/04/15 This version covers the updates since 2022/04/15, which mainly include the following important additions and improvements: - Released the Alipay+ Unified Payment edition of Cashier Payment. In this version, Alipay+ supports consulting the payment method information via the **consultPayment** API or the Alipay+ ACQP Client SDK. Since 2022/05/27, Alipay+ has supported the aggregated logo feature. - Added the support of the TSP integration mode for ACQPs. - Improve the API reference documentation in terms of the parameter descriptions, result codes, and so on. - Optimized the documentation of Reconciliation in terms of adding a guide about how to perform reconciliation, refining the parameter description and sample codes, and so on. - Added the documentation for support of BNPL channels. - Added the FAQ documentation for ACQPs. For more information about all the updates in Version 1.1.0, see the change history below. # History for previous updates > **Note**: Starting from 2022/07/29, the Alipay+ documentation is restructured to support version control. The following list describes important updates to our documentation before this date. ## July 15 2022 ### Enhanced features - Changed the _merchantInfo.registrationDetail.registrationNo_ parameter in the [registration](../api_acq/registration) API from `Required` to `Optional` to satisfy the needs of individual merchant registration. - Added the following 6 valid values to the _pspRegistrationResultList.pspName_ parameter in the [inquiryRegistrationStatus](../api_acq/inquiry_registration_status) and [notifyRegistrationStatus](../api_acq/notify_registration_status) APIs to keep consistent with the newly-launched feature for merchant registration at MPP's side: - `BPI` - `RABBIT_LINE_PAY` - `BOOST` - `NaverPay` - `KLARNA` - `TINABA` ### Document improvements - Improved the Reconcile section in that: - Optimized the Overview topic to include information about some basic concepts about the reconciliation. - Added a topic Perform reconciliation to introduce a step-to-step guide on how to do reconciliations. - Updated the samples and the description of the parameters in each financial report. - Added a subsection Explore more to introduce miscellaneous information, for example, how to select the reconciliation mode, and how to handle exceptional cases. - Removed the following 25 request parameters from the specification of the [registration](../api_acq/registration) API. Note that this change is backward compatible. - _merchantInfo.logo.logoName_ - _merchantInfo.logo.logoUrl_ - _merchantInfo.merchantAddress.region_ - _merchantInfo.merchantAddress.state_ - _merchantInfo.merchantAddress.city_ - _merchantInfo.merchantAddress.address1_ - _merchantInfo.merchantAddress.address2_ - _merchantInfo.merchantAddress.zipCode_ - _merchantInfo.representativeName_ - _merchantInfo.representativeId_ - _merchantInfo.registrationDetail.attachments.attachmentType_ - _merchantInfo.registrationDetail.attachments.file_ - _merchantInfo.registrationDetail.attachments.attachmentName_ - _merchantInfo.registrationDetail.attachments.content_ - _merchantInfo.registrationDetail.attachments.contentType_ - _merchantInfo.registrationDetail.contactInfo.contactNo_ - _merchantInfo.registrationDetail.contactInfo.contactType_ - _merchantInfo.registrationDetail.registrationEffectiveDate_ - _merchantInfo.registrationDetail.registrationExpireDate_ - _merchantInfo.shareholderName_ - _merchantInfo.shareholderId_ - _storeInfo.feeTier_ - _storeInfo.storeContacts.fullName_ - _storeInfo.storeContacts.identificationId_ - _storeInfo.storeContacts.contactNo_ ## June 30 2022 ### Document improvements - Updated the API reference documentation, to make it more accurate and clear. This includes: - Added more detailed descriptions. For example, for optional request parameters, added conditions when these parameters are recommended to be specified by the ACQP; for optional response parameters, added conditions when these parameters are returned by Alipay+. - Refined the _Result processing logic_ section for APIs that are invoked by the ACQP. - Added the _How to return the result_ section for APIs that are invoked by Alipay+. - Adjusted the sequence of some parameters based on their relevance. - Fixed several errors in the sample codes. - Fixed some grammatical errors to improve readability. For more information, see [API Reference (ACQP)](../api_acq). - Updated the Result codes table as follows: - Added the `NO_INTERFACE_DEF` result code for all APIs. - Added the `PAYMENT_AMOUNT_INVALID` result code for the following APIs: - **pay (Auto Debit)** - **pay (User-presented Mode Payment)** - **pay (Merchant-presented Mode Payment - Entry Code)** - **pay (Merchant-presented Mode Payment - Order Code)** - **pay (Cashier Payment)** - **userInitiatedPay** - Added the `ORDER_IS_CLOSED` result code for the **userInitiatedPay** API. - Added the `CURRENCY_NOT_SUPPORT` result code for the **refund** API. - Deleted the `INVALID_API` result code for all APIs. - Deleted the `EXPIRED_CODE` result code for the following APIs: - **pay (Merchant-presented Mode Payment - Entry Code)** - **pay (Merchant-presented Mode Payment - Order Code)** - **pay (Cashier Payment)** - Deleted the `INVALID_CODE` result code for the following APIs: - **pay (Merchant-presented Mode Payment - Entry Code)** - **pay (Merchant-presented Mode Payment - Order Code)** - **pay (Cashier Payment)** - Deleted the `REPEAT_REQ_INCONSISTENT` result code for the **registration** API. - Deleted the `REGISTRATION_STATUS_ABNORMAL` result code for the **notifyRegistrationStatus** API. - Released a step-by-step guide for merchants on how to consult the Alipay+ payment method information with Web/WAP SDK. For more information, see [Consult payment method information with SDK](../unified_for_merchant/consult_with_sdk). - Released the brand display guidelines for Cashier Payment for merchants. For more information, see [Brand Display Guidelines for Cashier Payment](../brand_guidelines/brand_cashier_acq). - Updated the brand display guidelines. This includes the following documents: - [Alipay+ Fundamental Brand Guidelines](../brand_guidelines/foundational_brand). The original [Alipay+ foundational brand guidelines](../brand_guidelines_older_edition/foundational_brand) is moved to older edition documents. - [Alipay+ Brand Mark Assets](../brand_guidelines/brand_assets). This provide an entry to download the Alipay+ logo asset. - [Brand Display Guidelines for Cashier Payment](../brand_guidelines/brand_cashier_acq). This replaces the UX design guideline for Cashier Payment. - [Brand display guidelines for in-store payment](../brand_guidelines/brand_in_store_acq). This replaces the Brand display guidelines for in-store payment in [UX design guideline](../ux/acq_overview). - Changed the term **Legacy Documentation** to **Older Edition**, because the Tile and Bundle Mode of Cashier Payment is still available for some clients, and its documentation is still maintained. For more information, see [Older Edition](../older_edition). ## May 27 2022 ### New features - Released the aggregated logo feature for Cashier Payment (Alipay+ Unified Payment). For more information, see [UX design guideline](https://docs.alipayplus.com/alipayplus/alipayplus/ux/ux_web.md) and [Product introduction](https://docs.alipayplus.com/alipayplus/alipayplus/integration_cashier_acq/cashier_payment_acq.md). - Released the TSP integration mode for ACQPs. In this mode, ACQPs can integrate Alipay+ products by cooperating with their TSPs. For more information, see the following three documents: - [Integration guide for TSP mode](../integration_tsp) - [Alipay+ Developer Center User Guide for Partners](../developer_center_acq) - [Alipay+ Developer Center User Guide for TSPs](../developer_center_tsp) ### Enhanced features - Added an entry to download the Alipay+ logo asset in [Alipay+ foundational brand guidelines](https://docs.alipayplus.com/alipayplus/alipayplus/brand_guidelines/foundational_brand.md). - Updated samples for the [inquiryRegistrationStatus](https://docs.alipayplus.com/alipayplus/alipayplus/api_acq/inquiry_registration_status.md) API to help ACQPs better specify request parameters and obtain the registration result. ### Document improvements - Deleted the _appIdentifier_ parameter in the [pay (cashier payment)](https://docs.alipayplus.com/alipayplus/alipayplus/api_acq/pay_cashier.md) API. - Added the enumeration values of the _paymentOptions_._promoNames_ parameter in the [consultPayment](https://docs.alipayplus.com/alipayplus/alipayplus/api_acq/consult_payment.md) API to include the usable languages for the promotion names. - Added a parameter _pspId_ to the response parameters in the [pay (cashier payment)](https://docs.alipayplus.com/alipayplus/alipayplus/api_acq/pay_cashier.md) API. - Changed the report names in the Reconcile section of all the integration documents to match the names in the Alipay+ Rules. Specifically: - **Clearing Transaction Report** is changed to **Transaction Detail Report**. - **Clearing Summary Report** is changed to **Transaction Summary Report**. - **Clearing Fee Report** is changed to **Fee Report**. - Deleted the _scopes_ parameter from [the idempotency fields](https://docs.alipayplus.com/alipayplus/alipayplus/api_acq/idempotency.md) table as it can not be used to control the idempotency for the **prepare** API. ## April 29 2022 ### New features - Released the migration guide doc for AlipayCN to Alipay+. For more information, see [Migration guide from AlipayCN to Alipay+](../migration). - Released the migration guide documentation for AMS to Alipay+. For more information, see [Migration guide from AMS to Alipay+](../migrate_ams_aps). - Released the documentation for support of BNPL channels. For more information, see [Best practices for BNPL channels](../bnpl). - Released the FAQ documentation for ACQPs. For more information, see [FAQ](../integration_faq_acq/faq). ### Enhanced features - Split the **consultPayment** API reference into two topics, one for Cashier Payment, one for Auto Debit. For more information, see [consultPayment (Cashier Payment)](../api_acq/consult_payment) and [consultPayment (Auto Debit)](../api_acq/consult_payment_auto). - Updated the UX design guidelines for Cashier Payment and moved the old version to Older Edition. For more information, see [UX Design Guidelines](../ux) and [Older Edition](../older_edition/doc). ### Document improvements - Updated the notification retry period from "up to 24 hours" to "up to 24 hours 22 minutes" for the **notifyPayment** API. - Changed the accuracy of the **Request-Time** and **Response-Time** header fields from milliseconds to seconds. - Changed the conditionality of the following parameters from Required to Optional for the **consultPayment** API: - _merchant.merchantMCC_ - _merchant.merchantName_ - _merchant.merchantAddress_ ## April 15 2022 ### New features - Released the Alipay+ Unified Payment edition of Cashier Payment. For more information, see [Product introduction](../integration_cashier_acq/cashier_payment_acq). - Released the Alipay+ ACQP Client SDK. For more information, see [SDK Reference](../sdk_acq/sdk_overview). - Added older edition documentation for Cashier Payment tile and bundle mode. For more information, see [Older Edition](../older_edition/doc). ### Enhanced features - Upgraded the [pay](../api_acq/pay_cashier) and [consultPayment](../api_acq/consult_payment) APIs for the Alipay+ Unified Payment edition of Cashier Payment. ## March 31 2022 ### New features - Added a glossary of terms that are used in Alipay+ for your convenience. For more information, see [Glossary](../glossary/v1). ### Fixed bugs - Fixed the spelling of the following parameters in the Clearing Transaction Report and Clearing Fee Report: - Updated _orignalTransactionRequestId_ to _originalTransactionRequestId_. - Updated _feeSettleAmountValue_ to _feeSettlementAmountValue_.