Search...
APIJSLog inGet started
Airwallex logo
Home
Platform APIs
Connected Accounts
Accounts
Payments
Transactional FX
Payouts
Issuing
Back to home
OverviewHow connected accounts workSupported regions
Get started
Onboard connected accountsKYC and onboarding
Handle KYC RFI
KYB and onboarding
Embedded KYB componentHosted Onboarding Native API
Payment Method Onboarding Requirement
Handle Payment Enablement RFI
Handle Transaction RFI
Onboard multiple connected accounts

Native API

Overview

These are the steps to fully activate a payment method:

  1. Provide store information using accounts API

    a. For new accounts, the platform can send the store information in the create account API.

    b. For existing accounts, the platform can send the store information through account amendment API.

  2. Request to enable payment method capabilities on demand after KYC pass.

  3. Polling or waiting for webhooks to check capability status until the capability status becomes ENABLED. The ENABLED status indicates that AIRWALLEX has activated the payment method and you can start transacting. When the capability status is PENDING, more information could be asked through RFI for the evaluation of Airwallex. When the capability status is DISABLED, you can find the detailed reasons in the reason_codes and reapply if applicable.

  4. (Optional) Some customers might require reserves and you can use api or webhook to query the reserve terms.

Step 1-A Create account with store details

POST /api/v1/accounts/create

  • Description
    • There is new field store_details in the account_details structure for business accounts.
    • store_details can be updated with the update API before submission. store_details applies to all versions.
  • Here is a sample payload with version 2023-06-15. Please refer to store detail requirement for detailed requirements
JSON

Step 1-B Add store details - for existing accounts

POST /api/v1/account/amendments/create

  • Description
    • Before enabling the payment method capabilities, the store details can be amended and the latest data can be obtained from the GET /api/v1/accounts/{id} API.
    • Before enabling the payment method capabilities, the status of the amendment will always be APPROVED.
    • Available amend target
      • account_details.store_details
    • Amendment status
      • PENDING
      • APPROVED
      • REJECTED
  • Header
    • x-on-behalf-of: $connected_account_open_id

Request body

JSON

Response body

JSON

GET /api/v1/account/amendments/{amendment_id}

  • Description
    • Get the amendment details of past amendments.
  • Header
    • x-on-behalf-of: $connected_account_open_id

Response body

JSON

Step 2 Enable payment method capability

This step is to apply for both the account capability to use payment methods and also the payment method activation for the store. When the capabilities are granted, the corresponding payment methods are activated.

POST /api/v1/account_capabilities/{capability_id}/enable

  • Description

    • Available capability IDs

    • Capability status - PENDING - ENABLED - DISABLED If there are multiple capabilities to be enabled, the request should be sent sequentially and those capabilities will be processed together.

  • Header

    • x-on-behalf-of: $connected_account_open_id

Request body

JSON

Response body

JSON

Step 3 Check capability status

Response body

JSON

Webhook: account_capability.enabled webhook

payload

JSON

For disabled payment methods, you can find the detailed reasons in the reason_codes

Response body

JSON

Reason_codes details

reason_codesDetails
WEBSITE_FAIL_AFTERPAY_REQUIREMENT(1) Website must have more than 3 months of history.
(2) Website can only sell products in these currencies: AUD, NZD, CAD, GBP, USD
WEBSITE_FAIL_INDONESIA_REQUIREMENT(1) Website must have a fully localized Bahasa Indonesia version.
(2) Prices must be displayed in IDR (Indonesian Rupiah)
WEBSITE_FAIL_JAPAN_REQUIREMENT(1) Website must have a fully localized Japanese version.
(2) Required Information in Japanese (Preferably present all the information on one page, titled 'NOTATION PAGE' or '特定商取引法に基づく表記')
- Company name and the name of the responsible sales representative/officer
- Company office address
- Contact information (phone & email), including operation hours
- Payment method names (e.g., Credit Card, Konbini, Pay-easy, PayPal)
- Refund policy and shipment policy (including fees and delivery times)
(3) Telephone Requirements: A phone number operated by Japanese speakers must be publicly available. Mobile and forwarded numbers are not allowed. Domestic call rates must apply—international call rates are prohibited.
WEBSITE_HAS_REDIRECT_URLYour website should not redirect users to external sites
WEBSITE_INDUSTRY_MISMATCHThe nature of your website must align with the industry specified in your application
WEBSITE_LEGAL_NAME_MISMATCHYour website must display your legal entity name
WEBSITE_NO_ABOUT_US_PAGEYour website must display an about us section with business description
WEBSITE_NO_CHECKOUTYour website must have a working checkout section with pricing & product info
WEBSITE_NO_CONTACT_INFOYour website should clearly display your contact information (address, email, phone number)
WEBSITE_NO_PRIVACY_POLICYYour website should include a privacy policy
WEBSITE_NO_SHIPPING_POLICYYour website should display a shipping & refund Policy
WEBSITE_NO_TERMS_CONDITIONYour website should display terms & conditions
WEBSITE_REGISTRATION_ADDRESS_MISMATCHYour website must display your business registration address
WEBSITE_REGISTRATION_NUMBER_MISMATCHYou website must display your business registration number

Step 4 Check reserve terms

Some customers might require reserves and you can use api or webhook to query the reserve terms. You can learn more about reserve here

GET /api/v1/pa/config/reserve_plan

  • Header
    • x-on-behalf-of: $connected_account_open_id

Response body

JSON

Webhook: reserve_plan.updated webhook

Payload

JSON

Additional Requirement for US Merchants

If your merchant is registered in the US, you'll need to submit the following additional requirements in account details to use payments.

  1. US person information (account_details.business_person_details)
  • At least one US person with SSN or ITIN is required (account_details.business_person_details.identifications.primary.tax_id.type)
  • The US person can be one of the following role: AUTHORISED_PERSON, BENEFICIAL_OWNER, CONTROLLING_PERSON (account_details.business_person_details.roles)
  • Date of Birth is mandatory (account_details.business_person_details.date_of_birth)
  • Full address of the US person should be provided, including:
    • Address line 1 should mandatorily have a house number (account_details.business_person_details.residential_address.address_line1)
    • Postal code is mandatory (account_details.business_person_details.residential_address.postcode)
    • Two-letter state code is mandatory if it's a US state e.g. CA for California (account_details.business_person_details.residential_address.state)
  1. Primary contact details
  • Contact email is mandatory (primary_contact.email)
  • Contact mobile number is mandatory (primary_contact.mobile)
Was this page helpful?
On this page
Was this page helpful?