Micro-deposit verification

Account verification is highly recommended to prevent fraudulent disputes. Airwallex offers micro-deposit services to help verify ownership of the bank account provided by the shopper. After the checkout form is submitted, Airwallex will send two micro-deposits to the owner’s bank account and an email with the verification link to the shopper. Sample email as below:

The two micro-deposits may take up to two days to appear on the shopper’s online statement with description “{Merchant Name}”. After the shopper receives the micro-deposits, they can enter the two amounts on the verification form (redirected from email link) to verify the account. Please be aware that the shopper has a maximum of three attempts to verify the account. If shopper exceeds this limit, Airwallex cannot verify the bank account and the checkout will need to be performed again.

Use cases

Micro-deposits are most commonly used for linking bank accounts for recurring payments. Due to the lead time of micro-deposit arrival and verification, the service is best suited for post-paid use cases of non-financial services, when the shopper can access the service before the account is verified.

Triggering mechanism

After payment submission, if the transaction is marked as high risk by Airwallex fraud scanning, micro-deposit verification will be triggered.

If you want to skip verification for all transactions, you can choose to override your global fraud settings on individual payments by providing a different value when you create a PaymentIntent.

Shell

skip_risk_processing is only allowed if Airwallex has configured this fraud setting on your merchant account. If you provide a value that is not allowed based on your default settings, your payment request will be rejected. If you encounter any issues with these settings, contact your Airwallex Account Manager.

Hosted Payment Page (HPP) integration

If integrating with HPP, please follow the HPP integration guide and note the following:

1. When shoppers complete payment information details and submit the form, they will be redirected back to your client-side by the successUrl . Clear messaging on your client-side about what these micro-deposits are and how you can use them can help your shoppers avoid verification issues. A notification sample is shown below. If the successUrl is not provided, Airwallex will redirect your shoppers to the default notification page.

This account cannot be charged at the moment, please verify the account

You will receive two micro-deposits to your account in 1-2 business days. You can click the verify button or verify through the email we have sent you.

2. Airwallex also recommends that you provide the verification link on your client-side to help your shoppers verify the account easily.

The verification link is returned to you in the PaymentIntent via the PaymentIntents API.

3. When shoppers click the verify link, they will be redirected to the Airwallex verification service. Shoppers can provide the two amounts from their bank statements and verify the account. We recommend you provide your successUrl so that shoppers can be redirected to your client-side after they complete verification.

4. You should also consider a reset or an update link on your client-side to launch the checkout form again. This will allow shoppers to try a new payment method or update their payment information if they are unable to provide micro- deposit verification.

Drop-in and Embedded Elements integration

If integrated with Drop-in Element or Embedded Elements, follow the Drop-in and Embedded Elements integration guides and note the following:

You should provide clear messaging about what these micro-deposits are and how you can use them to help your shoppers complete verification, as Airwallex cannot redirect your shoppers to the default verification notification page. A notification sample is shown as above in the HPP section.
Airwallex also recommends that you provide a verification link on your client-side to help your shoppers verify the account easily.
The verification link is returned to you in the PaymentIntent via the PaymentIntents API.

You should also consider a reset or update link on your client-side to launch the checkout form again. This will allow shoppers to try a new payment method or update the payment information if they are unable to provide micro-deposit verification.

Native API integration

If integrated with API, please follow the API integration guide and note the following:

You should have clear messaging about what these micro-deposits are and how you can use them to help your shoppers avoid verification issues, as Airwallex cannot redirect your shoppers to the default verification notification page. A notification sample is shown as above in the HPP section.
Airwallex recommends that you provide a return_url during payment_intents/create so that your shoppers will be redirected to your site after submitting the checkout form.
You can render the verification link on your client-side using the verification URL returned in payment_intents/{id}/confirm response, so that your shoppers can also enter verification form from your portal.
You should also consider a reset or update link on your client-side to launch the checkout form again. This will allow shoppers to try a new payment method or update the payment information if they are unable to provide micro-deposit verification.

Notifications from Airwallex

Airwallex will notify you of the payment result asynchronously via the webhook API. Please refer to the Webhook guide to set up your webhooks accordingly.

You can display the verification status on your client side to guide your shoppers to the next step. It is recommended to subscribe to the payment_intent.succeeded and payment_intent.requires_customer_action webhooks which indicates that the the account is verified and pending verification respectively.

You may also query the status of a payment anytime via the PaymentIntents API.