Auto Debit provides consumers with a password-free payment experience. After the consumer binds an account to the merchant and gives the authorization, the merchant can deduct funds from the consumer's account by using an access token. Auto Debit is available in different payment scenarios, including one-time payments and recurring payments.

Basic concepts

User experience

With Auto Debit, the consumer can place an order on the merchant platform and select Alipay+ as the payment method. Then Alipay+ displays the available MPPs for the consumer to select one and bind the MPP account to the merchant platform and authorize the merchant to deduct funds from the bound account. After the accounting binding is done, the consumer can return to the merchant platform and use the bound account to pay.

Account binding

This section describes the user experience for the account binding, which can be done in the MPP app, WAP page, or website.

For different MPP platforms, the user experience is different. The MPP platform can be a desktop website (referred to as "Web" below) or a mobile app/WAP page (referred to as "Mobile" below).

• If the consumer places the order on a Mobile page, the consumer is redirected to the MPP app or WAP page to continue the payment process.
• If the consumer places the order on a Web page, the consumer is redirected to a Web page to continue the payment process.

Mobile

This section introduces the user experience of account binding on mobile terminals.

App

In this scenario, the MPP app is installed on the consumer's phone, and the consumer starts the binding process in the merchant app.

After placing an order in the merchant app, the consumer is redirected to the MPP app to complete the account binding. The following figure illustrates the user experience for this scenario:

Figure 1. Account binding process in the MPP app

The consumer performs the following steps to complete the accounting binding:

1. The consumer selects Alipay+ in the merchant app.
2. The merchant redirects the consumer to an Alipay+ page to select an MPP to bind.
3. Alipay+ redirects the consumer to the MPP side to sign the authorization agreement.
4. The consumer completes the verification and binds the MPP account as the payment method to be used for transactions on the merchant platform.
5. The MPP app presents the authorization result to the consumer.
6. The consumer is redirected back to the merchant.

WAP page

In this scenario, the MPP app is not installed on the consumer's phone, and the consumer starts the binding process on the merchant page.

After placing an order on the merchant WAP page, the consumer is redirected to the MPP WAP page to complete the accounting binding. The following figure illustrates the user experience for this scenario:

Figure 2. Account binding process on the MPP WAP page

The consumer performs the following steps to complete the accounting binding:

1. The consumer selects Alipay+ on the merchant page.
2. The merchant redirects the consumer to an Alipay+ page to select an MPP to bind.
3. Alipay+ redirects the consumer to the MPP side to log in.
4. The consumer completes the login verification and signs the authorization agreement to bind the MPP account as the payment method to be used for transactions on the merchant platform.
5. The MPP WAP page presents the authorization result to the consumer.
6. The consumer is redirected back to the merchant.

Web

This section introduces the user experience of account binding on Web terminals. Depending on whether the MPP app supports code scanning, the payment experience varies:

• If the MPP app supports code scanning, the consumer scans the code and completes the payment by using the MPP app.
• If not, the consumer is redirected to a series of WAP pages to go through the payment process, including login and paying with a password.

Scan to bind account

In this scenario, the consumer's MPP app supports code scanning.

After placing an order on the merchant Web page, the consumer can use the MPP app to scan the authorization QR code on the merchant page to complete the account binding. The following figure illustrates the user experience for this scenario:

Figure 3. Account binding process by scan-to-authorize

The consumer performs the following steps to complete the accounting binding:

1. The consumer selects Alipay+ on the merchant page.
2. The merchant redirects the consumer to an Alipay+ page to select an MPP to bind.
3. Alipay+ redirects the consumer to the MPP Web page, where a QR code is displayed.
4. The consumer uses the MPP app to scan the QR code to sign the agreement, complete the verifications, and complete the authorization.
5. The MPP app displays the authorization result.
6. The merchant Web page displays the authorization result.

Log in to bind account

In this scenario, the consumer places an order on the merchant's desktop website but the MPP app that the consumer pays with does not support scan-to-pay.

After placing an order on the merchant Web page, the consumer is redirected to the Alipay+ checkout page. The consumer then selects an MPP and logs in to the MPP page to complete the account binding. The following figure illustrates the user experience for this scenario:

Figure 4. Account binding process by login-to-authorize

The consumer performs the following steps to complete the accounting binding:

1. The consumer selects Alipay+ on the merchant page.
2. The merchant redirects the consumer to an Alipay+ page to select an MPP to bind.
3. Alipay+ redirects the consumer to the MPP Web page to log in.
4. The consumer logs in and completes the verifications.
5. The MPP redirects the consumer to the authorization page, where the consumer signs the authorization agreement and binds the MPP account as the payment method to be used for transactions on the merchant platform.
6. The MPP page displays the authorization result.
7. The consumer is redirected back to the merchant.

Payment with a bound account

After binding an MPP account to the merchant, the consumer can pay for Auto Debit transactions with the bound account at the merchant side. The following figures illustrate the payment process on the mobile side and on the web side:

Figure 5. Payment with a bound account on the mobile side

1. The consumer selects the MPP as the payment method on the merchant cashier page.
2. The consumer clicks the pay button to pay.
3. The merchant displays the payment result page to the consumer.

Product functionalities

Alipay+ Auto Debit offers the following main features to facilitate your business::

How it works

The following figure illustrates the process of how Auto Debit works:

Figure 6. Auto Debit workflow

Key steps

• For the account binding flow:

1. The MPP sends the authorization page URL to Alipay+ via the prepare API. (Step 3)
2. The MPP renders and displays the authorization page and returns the authorization code to the merchant/ACQP after the binding succeeds. (Step 6 to 9)
3. The MPP sends the access token to Alipay+ via the applyToken API. (Step 12)

• For the payment Flow: The MPP accepts and processes the payment initiated with the access token, and directly returns the payment result. (Step 16 to 17)

Page detail requirements

This section introduces the requirements of the page details for the following important pages for Auto Debit:

• Authorization Confirmation Page
• Transaction Detail Page

Authorization Confirmation Page

The following figure illustrates the fields that can be displayed on the Authorization Confirmation Page for Auto Debit.

Note: The design of the figure is for reference only.

Figure 7. Fields for Authorization Confirmation Page

The following table lists additional information about the fields in figure 7.

If the fields in the following table are available, the fields must be provided on the Authorization Confirmation Page.

Transaction Detail Page

The following figure illustrates the fields that can be displayed on the Transaction Detail Page for Auto Debit.

Figure 8. Fields for Transaction Detail Page

The following table lists additional information about the fields in figure 8. Information on all of the fields in the table can be obtained from the related payment APIs.

If the fields in the following table are available, the fields must be displayed on the Transaction Detail Page.

Get started

To get started with Cashier Payment integration, see Integration in the Auto Debit integration guides.