Accept DANA on your website by redirecting your customer to DANA cashier. See checkout experience as below

![DANA - desktop website browser](//images.ctfassets.net/c3n7jozh84hr/knCdy7G1Xng8Wt6usl9ol/84ca397cd2e8436ceb15a1e8422f4ba2/image.png)

1. The shopper chooses to pay with DANA and is redirected to DANA login page
2. The shopper logs in to his/her DANA account and completes payment
3. Payment succeeds and the shopper is redirected back to the page you designated

Step 1. Initialize a payment Intent

Step 2. Redirect to DANA Cashier to complete payment

Desktop Website Browser

Accept DANA on your mobile website by redirecting shoppers to DANA Cashier. See checkout experience as below
1. The shopper chooses to pay with DANA and proceed payment with mobile browser
2. The shopper login to DANA account in browser and completes the payment
3. Payment succeeds and the shopper is redirected back to the page you designated


Mobile Website Browser

Gain access to shoppers on DANA

Functionalities and value-added features supported

Countries and currencies supported

Choose the integration method that best suit your needs

Accept desktop and mobile payments from your shoppers with DANA

DANA

DANA is a digital payment service platform based in Indonesia that offers payments, loyalty points and financial services. DANA users can carry out a wide range of electronic transactions through services such as DANA Balance, Bank Transfers, Credit Cards, as well as Cash Deposits to minimarkets. It has 35 million total users and deposited funds of 21.06 million USD on the platform as of the end of 2019. 


| Features     | DANA    |
| ---------- | ---------- |
| Merchant supported countries/regions | HK |
| One-off payment | ✅|
| One-off payment with 3DS      | ⛔|
| Recurring Payment | ✅|
| Refunds | ✅|
| Partial Refunds | ✅|
| Disputes/Chargeback | ✅|

| Country & Region     | Transaction Currency    | Settlement currency |
| ---------- | ---------- |
| HK | IDR | USD| 


The amount limitation for each transaction is from 300 IDR to 2,000,000 IDR


Note

Airwallex has built a range of client-side integration methods that allows you to manage your UI, minimises your implementation effort and allows you to get to market quickly.

| Integration Type     | Supported    | Requires PCI-DSS    |
| ---------- | ---------- | ---------- | 
| HPP | ✅| No|
| Embedded Fields | ✅| No|
| Drop-in Elements      | ✅| No|
| API      | ✅| No|

Airwallex’s solution supports DANA payment acceptance desktop and mobile channels.

| dana    | Destop Website Broswser      | Mobile App     | Mobile Webiste Broswer     |
| ---------- | ---------- | ---------- | ---------- |
| One-off Payment       |  ✅    |   ⛔    | ✅     |
| Recurring Payment       | ✅       |   ⛔     |   	✅     |

The Embedded fields integration is a set of prebuilt UI components, like inputs and buttons, that merchants can directly integrate into their checkout page.  This integration enables merchants to accept payments by partially delegating the responsibility of payment processing to Airwallex while still maintaining control of the overall look and feel of their checkout page.  This integration requires a limited PCI-DSS certification.
The main distinctive features include:

- Automatic formatting card information (card number, expiry, cvc) while entered
- Customizable placeholders to fit your UX design
- Usage of responsive design to fit the width of your customer’s screen or mobile device
- Customizable styling to match the look and feel of your checkout flow
- Limited PCI-DSS scope suitable for partners with a PCI-DSS SAQ

There are currently 5 embedded fields integrations, click on each element for a specific guide on their integration using [airwallex-payment-elements](https://www.npmjs.com/package/airwallex-payment-elements):

- [Card](https://github.com/airwallex/airwallex-payment-demo/blob/master/docs/card.md), a single row input container with card number, expiry date, and cvc input
- [Full Featured Card](https://github.com/airwallex/airwallex-payment-demo/blob/master/docs/fullfeaturedcard.md), a multi-input field container with card number, expiration date, security code, name on card, and a checkout button
- [Split Card](https://github.com/airwallex/airwallex-payment-demo/blob/master/docs/splitcard.md), individual card input fields including card number, expiry date, and cvc
- [Wechat](https://github.com/airwallex/airwallex-payment-demo/blob/master/docs/wechat.md), a Wechat pay QR code
- [Redirect](https://github.com/airwallex/airwallex-payment-demo/blob/master/docs/redirect.md), a checkout button that redirects customers to a specified payment method

The following steps will give you a high-level overview of implementing a card element. Refer to our [Card Element guide](https://github.com/airwallex/airwallex-payment-demo/blob/master/docs/card.md) for the complete details of the integration, and explore the links above for other element integrations.  This integration uses our lightweight Javascript SDK, [airwallex-payment-elements](https://www.npmjs.com/package/airwallex-payment-elements).  

1. Create a Payment Intent through the Airwallex API - [see full details here](https://www.airwallex.com/docs/api#/Payment_Acceptance/Payment_Intents/Intro).  To execute a payment checkout, we must have a Payment Intent that captures the details of your checkout, including the currency and amount you wish to charge your customer.  We will need the `intent id` and `client secret` to checkout.

See how to [create a payment intent](https://www.airwallex.com/docs/api#/Payment_Acceptance/Payment_Intents/_api_v1_pa_payment_intents_create/post) with the Airwallex API for an example of intent details.

2. On your checkout, integrate with airwallex-payment-elements to create a card element using the Airwallex `createElement` function and a checkout button bound to the Airwallex `confirmPaymentIntent` function.  The card element will collect sensitive payment details from the customer and the checkout button will trigger the actual payment that confirms and fulfills the payment intent.  You must provide the `intent_id` and `client_secret` in the `confirmPaymentIntent` function.

See [an example](https://github.com/airwallex/airwallex-payment-demo/blob/master/integrations/cdn/card.html#L56) of how the card element can be integrated in Static HTML or refer to the [Card Element Guide](https://github.com/airwallex/airwallex-payment-demo/blob/master/docs/card.md) for complete integration details.

3. Once the element is successfully mounted, the card element will handle the payment process.  Upon completion of the checkout, you will receive a promise which will inform you of whether the transaction was successful or ran into an error.  You can then process this response and proceed to the next steps of your checkout flow.

Ready to integrate?  See our [copy-paste ready demos](https://github.com/airwallex/airwallex-payment-demo) for 5 different web frameworks!


Embedded Fields Integration

Mobile App 

Mobile Website Browser 

Gain access to shoppers on Alipay

Accept omni-channel payments from your shoppers with Alipay

Alipay

Accept Alipay on your mobile app on your shopper’s Android or iOS phone. You can choose to integrate Airwallex mobile SDK that supports multiple payment methods.  See checkout experience as below
![Alipay - mobile app](//images.ctfassets.net/c3n7jozh84hr/5bscTHfuOUnn6XEEijLNbV/d2697ef9987bf7f1202830f7fda7582c/image.png)

1. The shopper chooses to pay with Alipay
2. The shopper reviews transactions and confirm to pay
3. The shopper is redirected to Alipay App and completes payment 
4. ayment succeeds and the shopper is redirected back to your App


Step 2. Redirect to Alipay App to complete payment

Accept Alipay on your mobile app on your shopper’s Android or iOS phone. You can choose to integrate Airwallex mobile SDK that supports multiple payment methods.  See checkout experience as below
![Alipay - mobile website browser](//images.ctfassets.net/c3n7jozh84hr/3kXYUncoZFFG3nIX7qB2TR/4843a2d18ed0e924bcf89c24056f5655/image.png)

1. The shopper chooses to pay with Alipay and proceed payment with mobile browser
2. The shopper login to Alipay account in browser and completes the payment
3. Payment succeeds and the shopper is redirected back to the page you designated


Step 2. Redirect to Alipay Cashier to complete payment

Mobile App

Gain access to shoppers on AlipayHK

Accept omni-channel payments from your shoppers with AlipayHK

AlipayHK

Accept Alipay HK on your mobile app on your shopper’s Android or iOS phone. You can choose to integrate Airwallex mobile SDK that supports multiple payment methods.  See checkout experience as below

1. The shopper chooses to pay with Alipay HK
2. The shopper reviews transactions and confirm to pay
3. The shopper is redirected to Alipay HK App and completes payment 
4. Payment succeeds and the shopper is redirected back to your App


Step 2. Redirect to Alipay HK App to complete payment

Accept Alipay HK on your mobile website by redirecting shoppers to Alipay HK Cashier. See checkout experience as below

1. The shopper chooses to pay with Alipay HK and proceed payment with mobile browser
2. The shopper login to Alipay HK account in browser and completes the payment
3. Payment succeeds and the shopper is redirected back to the page you designated


Step 2. Redirect to Alipay HK Cashier to complete payment

Mobile Website Broswer

Gain access to shoppers on GCash

Accept desktop and mobile payments from your shoppers with GCash

GCash

Accept GCash on your mobile website by redirecting shoppers to GCash Cashier. See checkout experience as below

1. The shopper chooses to pay with GCash and proceed payment with mobile browser
2. The shopper login to GCash account in browser and completes the payment
3. Payment succeeds and the shopper is redirected back to the page you designated


Step 2. Redirect to GCash Cashier to complete payment

Gain access to shoppers on Kakao Pay

Accept omni-channel payments from your shoppers with Kakao Pay

Kakao Pay

Accept Kakao Pay on your mobile website by redirecting shoppers to Kakao Pay Cashier. See checkout experience as below

1. The shopper chooses to pay with Kakao Pay in mobile browser 
2. Kakao Pay App is launched and the shopper completes the payment in Kakao Pay
3. Payment succeeds and the shopper needs to switch back to the browser for redirection. 


Accept Kakao Pay on your mobile app on your shopper’s Android or iOS phone. You can choose to integrate Airwallex mobile SDK that supports multiple payment methods.  See checkout experience as below

1. The shopper chooses to pay with Kakao Pay
2. The shopper reviews transactions and confirm to pay
3. The shopper is redirected to Kakao Pay App and completes payment 
4. Payment succeeds and the shopper needs to switch back to your App for redirection


Step 2. Redirect to Kakao Pay App to complete payment

Mobile APP

Gain access to shoppers on Touch ‘n Go

Accept omni-channel payments from your shoppers with Touch ‘n Go

Touch ‘n Go

Accept Touch 'n Go on your mobile website by redirecting shoppers to Touch 'n Go Cashier. See checkout experience as below

1. The shopper chooses to pay with Touch 'n Go and proceed payment with mobile browser
2. The shopper login to Touch 'n Go account in browser and completes the payment
3. Payment succeeds and the shopper is redirected back to the page you designated


Step 2. Redirect to Touch 'n Go Cashier to complete payment

Accept Touch 'n Go on your mobile app on your shopper’s Android or iOS phone. You can choose to integrate Airwallex mobile SDK that supports multiple payment methods.  See checkout experience as below

1. The shopper chooses to pay with Touch 'n Go
2. The shopper reviews transactions and confirm to pay
3. The shopper is redirected to Touch 'n Go App and completes payment 
4. Payment succeeds and the shopper is redirected back to your App


Step 2. Redirect to Touch 'n Go App to complete payment

This table below includes the response codes that you might receive when processing transactions. Those response codes are returned by the issuers and reflect the outcome of the authorization process.

Issuer's response codes

AVS Codes

CVC2/CVV2 Codes

This section helps you understand the meaning of the result codes used in the acquiring world. 

- [Issuer response codes](https://www.airwallex.com/docs/payments__acquiring-codes__issuer's-response-codes)
- [AVS codes](https://www.airwallex.com/docs/payments__acquiring-codes__avs-codes)
- [CVC2/CVV2 codes](https://www.airwallex.com/docs/payments__acquiring-codes__cvc2cvv2-codes)

Acquiring Codes

The Drop-in element integration enables merchants to embed a container of payment checkout options directly on their website.  Through this element, merchants can accept payments by partially delegating the responsibility of payment processing to Airwallex, while still maintaining control of the overall look and feel of their checkout page.  This integration requires a limited PCI-DSS certification.

The following steps will give you a high-level overview of implementing a Drop-in Element. Refer to our [Drop-in Element guide](https://github.com/airwallex/airwallex-payment-demo/blob/master/docs/dropin.md) for the complete details of the integration.  This integration uses our lightweight Javascript SDK, [airwallex-payment-elements](https://www.npmjs.com/package/airwallex-payment-elements).  

1. Create a Payment Intent through the Airwallex API - [see full details here](https://www.airwallex.com/docs/api#/Payment_Acceptance/Payment_Intents/Intro).  To execute a payment checkout, we must have a Payment Intent that captures the details of your checkout, including the currency and amount you wish to charge your customer.  We will need the `intent_id` and `client_secret` to checkout.

See how to [create a payment intent](https://www.airwallex.com/docs/api#/Payment_Acceptance/Payment_Intents/_api_v1_pa_payment_intents_create/post) with the Airwallex API for an example of intent details.

2. Integrate with airwallex-payment-elements to create a drop-in element on your page using the Airwallex `createElement` function.  The Drop-in element will render the available payment methods and enable customers to select the one most applicable to them.  

See the [Drop-in Element Guide](https://github.com/airwallex/airwallex-payment-demo/blob/master/docs/dropin.md) for complete integration details.

3. Once the element is successfully mounted, the drop-in element will handle the payment process.  Upon completion of the checkout, you will receive event notifications, whether successful or erroneous.  You can configure event listeners on your webpage to listen to the event notifications.

See [an example](https://github.com/airwallex/airwallex-payment-demo/blob/master/integrations/cdn/dropin.html#L83) of how listeners are integrated in Static HTML.  See more details about interacting with elements in the [Airwallex Payment Elements Docs](https://github.com/airwallex/airwallex-payment-demo/tree/master/docs#interacting-with-elements).

Ready to integrate?  [See our copy-paste ready demos](https://github.com/airwallex/airwallex-payment-demo) for 5 different web frameworks!


Drop-in Integration

The Hosted Payment Page integration enables Merchants to redirect customers to an Airwallex-hosted checkout page.  Merchants can accept payments by delegating the full handling of payment processing and display of payment options to Airwallex, supporting merchants without a full PCI-DSS certification (those who can only fulfill a PCI-DSS SAQ).  

The following steps will give you a high-level overview of implementing a Hosted Payment Page checkout. Refer to our [Hosted Payment Page guide](https://github.com/airwallex/airwallex-payment-demo/blob/master/docs/hpp.md) for the complete details of the integration.  This integration uses our lightweight Javascript SDK, [airwallex-payment-elements](https://www.npmjs.com/package/airwallex-payment-elements).  

1. Create a Payment Intent through the Airwallex API - [see full details here](https://www.airwallex.com/docs/api#/Payment_Acceptance/Payment_Intents/Intro).  To execute a payment checkout, we must have a Payment Intent that captures the details of the checkout, including the currency and amount you wish to charge your customer.  We will need the `intent_id` and `client_secret` to checkout.

See how to [create a payment intent](https://www.airwallex.com/docs/api#/Payment_Acceptance/Payment_Intents/_api_v1_pa_payment_intents_create/post) with the Airwallex API for an example of intent details.

2. Integrate with airwallex-payment-elements to redirect your customer to an Airwallex payment page with the Airwallex `redirectToCheckout` function.  Place in the `intent_id` and `client_secret` retrieved in the previous step to redirect your customer to their payment page.  

You can customize the look and feel of the Hosted Payment Page by providing fonts, and also redirect customers back to your site after the payment by providing the successUrl, failUrl, and cancelUrl options.

When this function is triggered, Airwallex will take care of redirecting your customer, helping your customer select the most appropriate payment method, collecting their payment details, and eventually triggering the authentication. You need to do nothing, besides providing the intent details, to collect payments from your customers.

See the [HPP integration guide](https://github.com/airwallex/airwallex-payment-demo/blob/master/docs/hpp.md) for more details on customizations.

3. Upon payment completion, your customer will be redirected to the successUrl or failUrl provided in the previous step (or default Airwallex success or fail or cancel pages if you don’t provide the respective urls).  The final status of your payment will be sent to the endpoint you configured.

Your customer will be redirected to your return success or fail or cancel url, which will be appended with the payment intent id.

```curl
https://your-website-host/your-success-path?id=int_xxxxx
```

Ready to integrate?  [See our copy-paste ready demos](https://github.com/airwallex/airwallex-payment-demo) for 5 different web frameworks!


Hosted Payment Page Integration

This table below includes the response codes that you might receive when the Card Verification Value (CVV) code is being checked during the transaction process. These codes are also referred to as CVV2, CVC2.

|Code|Webapp Description|Description|
|---|-----------------|----------|
|M|Match|CVV2 Match|
|N|Not Match|CVV2 does not match|
|P|Unavailable or Not Applicable|Not processed (issuer temporarily unavailable)|
|S|Unavailable or Not Applicable|Visa only. CVV2 should be on the card, but the merchant indicates that it is not|
|U|Unavailable or Not Applicable|Visa only. Issuer does not participate in CVV2 service or participates but has not provided Visa with encryption keys, or both|
|U|Unavailable or Not Applicable|Mastercard only. CVC 2 Unverified|
|Space|Unavailable or Not Applicable|Visa only. No result|


This table below includes the response codes that you might receive when the Address Verification Service  (AVS) is performed. Please note that not all countries support AVS. AVS is widely supported in the United States, Canada, Australia, New Zealand and the United Kingdom.

|Code|Webapp Description|Description|
|-----|----------------|-----------|
|A|Partial Match|Address matches, but ZIP code does not match.|
|B|Unavailable or Not Applicable|Visa only. Street address match. Postal code not verified because of incompatible formats. (Acquirer sent both street address and postal code.)|
|C|Unavailable or Not Applicable|Visa only. Street address and postal code not verified because of incompatible formats. (Acquirer sent both street address and postal code.)|
|D|Match|Visa only. Street address and postal code match.|
|E|Unavailable or Not Applicable|Error response for Merchant Category Code.|
|F|Match|Visa only. Street address and postal code match. Applies to U.K. only.|
|G|Unavailable or Not Applicable|Visa only. Address information is unavailable; international transaction; non-AVS participant.|
|I|Unavailable or Not Applicable|Visa only. Address information not verified for international transaction.|
|M|Match|Visa only. Street addresses and postal code match.|
|N|Not Match|Neither address nor postal code matches.|
|P|Unavailable or Not Applicable|Visa only. Postal codes match. Street address not verified because of incompatible formats. (Acquirer sent both street address and postal code.)|
|R|Unavailable or Not Applicable|Retry, system unable to process or timed out.|
|S|Unavailable or Not Applicable|AVS currently not supported. U.S. issuers will not be able to send through this response code.|
|U|Unavailable or Not Applicable|Mastercard only. No data from issuer/Authorization Platform|
|U|Unavailable or Not Applicable|Visa only. Address not verified for domestic transaction. Address not verified for international transaction. Issuer is not an AVS participant, or AVS data was present in the request but issuer did not return an AVS result, or V.I.P. performed address verification on behalf of the issuer and there was no address record on file for this account.|
|W|Partial Match|Visa only. Nine-digit ZIP code matches, but address does not match.|
|W|Partial Match|Mastercard only. For U.S. addresses, nine-digit postal code matches, address does not; for address outside the U.S., postal code matches, address does not.|
|X|Match|Mastercard only. For U.S. addresses, nine-digit postal code and address matches; for addresses outside the U.S., postal code and address match.|
|X|Match|Visa only. Exact match, address, and nine-digit ZIP code match.|
|Y|Match|Mastercard only. For U.S. addresses, five-digit postal code and address matches.|
|Y|Match|Visa only. Street address and postal/ZIP match.|
|Z|Partial Match|Mastercard only. For U.S. addresses, five-digit postal code matches, address does not.|
|Z|Partial Match|Visa only. Five-digit ZIP code matches, but address does not match or street address not included in request.|


| Code | Description|
| -----|-------------|
|00| Approved or completed successfully|
|01| Refer to card issuer |
|02| Visa only. Refer to card issuer, special condition (can only be used by non-Visa transactions and Japan domestic transactions). |
|03|Invalid merchant or service provider|
|04|Pick up card (no fraud)|
|05|Do not honor|
|06|Error|
|07|Visa only. Pick up card, special condition (fraud account)|
|08|Mastercard only. Honor with ID|
|10|Partial approval|
|11|Visa only. Approved (V.I.P)|
|12|Invalid transaction|
|13|Invalid amount or currency conversion field overflow|
|14|Invalid card number (no such number)|
|15|No such issuer. Invalid issuer|
|19|Visa only. Re-enter transaction|
|21|Visa only. No action taken|
|25|Visa only. Unable to locate record in file|
|28|Visa only. File temporarily not available for update or inquiry|
|30|Mastercard only. Format error|
|39|Visa only. No credit account|
|41|Lost card, pick up (fraud account)|
|43|Stolen card, pick up (fraud account)|
|46|Visa only. Closed Account (effective 17 April 2021)|
|51|Insufficient funds/over credit limit|
|52|Visa only. No checking account|
|53|Visa only. No savings account|
|54|Expired card or expiration date is missing|
|55|Incorrect PIN or PIN missing|
|57|Transaction not permitted to issuer/ cardholder|
|58|Transaction not permitted to acquirer/ terminal|
|59|Visa only. Suspected fraud|
|61|Exceeds withdrawal amount limit|
|62|Restricted card (card invalid in region or country)|
|63|Security violation|
|64|Visa only. Transaction does not fulfill AML requirement|
|65|Exceeds withdrawal count limit (deprecated)|
|65|Additional customer authentication required (formerly: Exceeds withdrawal count limit)|
|70|PIN Data Required (Europe only)|
|70|Contact Card Issuer|
|71|Mastercard only. PIN not changed|
|75|Allowable number of PIN entry tries exceeded|
|76|Visa only. Unsolicited reversal-reversal with no original transaction in history. V.I.P. unable to match reversal request to an original message|
|76|Mastercard only. Invalid/nonexistent "To Account" specified|
|77|Mastercard only. Invalid/nonexistent "From Account" specified|
|78|Visa only. Blocked, first used (Brazil only, effective 17 April 2021). Account is temporarily blocked for all transactions|
|78|Mastercard only. Invalid/nonexistent account specified.|
|79|Visa only. Already reversed (by Switch)|
|80|Visa only. No financial impact|
|81|Visa only. Cryptographic error found in PIN (used for cryptographic error condition found by security module during PIN decryption)|
|81|Mastercard only. Domestic debit transaction not allowed|
|82|Visa only. Negative CAM, dCVV, iCVV, or CVV results|
|82|Mastercard only. Timeout at issuer|
|84|Mastercard only. Invalid authorization life cycle|
|85|Visa only. No reason to decline a request for address verification, CVV2 verification, or a credit voucher or merchandise return|
|85|Mastercard only. Not declined (Valid for all zero amount transactions)|
|86|Cannot verify PIN|
|87|Mastercard only. Purchase amount only, no cash back allowed|
|88|Mastercard only. Cryptographic failure|
|89|Unacceptable PIN— Transaction Declined— Retry|
|91|Authorization System or issuer system inoperative|
|92|Financial institution or intermediate network facility cannot be found for routing (receiving institution ID is invalid). Unable to route transaction|
|93|Transaction cannot be completed - violation of law|
|94|Duplicate transmission.Transaction submitted containing values in tracing data fields that duplicate values in a previously submitted transaction. Note: This code is available in SMS raw data in case of duplicate transmission.|
|96|System malfunction or certain field error conditions|
|1A|Visa only. Additional Customer Authentication Required (Europe only)|
|B1|Visa only. Surcharge amount not permitted on Visa cards or EBT food stamps (U.S. acquirers only)|
|B2|Visa only. Surcharge amount not supported by debit network issuer.|
|N0|Visa only. Force STIP. Issuers use code when they cannot perform authorization but want STIP to perform it.|
|N3|Visa only. Cash service not available|
|N4|Visa only. Cash request exceeds issuer or approved limit|
|N5|Visa only. Ineligible for resubmission|
|N7|Visa only. Decline for CVV2 failure|
|N8|Visa only. Transaction amount exceeds preauthorized approval amount|
|P5|Visa only. Denied PIN unblock-PIN change or unblock request declined by issuer|
|P6|Visa only. Denied PIN change-requested PIN unsafe|
|Q1|Visa only. Card Authentication failed Or Offline PIN authentication interrupted|
|R0|Visa only. Stop Payment Order|
|R1|Visa only. Revocation of Authorization Order|
|R2|Visa only. Transaction does not qualify for Visa PIN|
|R3|Visa only. Revocation of all Authorizations order|
|Z3|Visa only. Unable to go online; offline-declined|


Category codes

Merchant Category Codes

Cardholder management APIs allow you to manage the named individuals in your organisation who hold cards. These APIs only allow you to modify the cardholder resources; to modify cards associated with a cardholder, pass the `cardholder_id` into the [Manage a Cardholder API](https://www.airwallex.com/docs/api#/Issuing/Cardholders/_api_v1_issuing_cardholders_create/post "Manage Cardholder APIs"). 

Sample Request

Manage Cardholders

The cardholder object is the resource associated with a named individual who is a representative of your business and will hold cards associated to them. Creation of cardholders involves passing our KYC (Know-Your-Customer) process and so individuals are required to present contact details as well as the details of their identifying documents.

To create a cardholder, use the [Create a Cardholder API](https://www.airwallex.com/docs/api#/Issuing/Cardholders/_api_v1_issuing_cardholders_create/post "Create Cardholder API"). A successful request returns a `cardholder_id` which can be passed into the other Issuing Card APIs to create and manage the cardholder's cards. 

__Please note:__

1. The ID requirements vary depending on the region in which your business resides. Please read the field decriptions in the [Create a Cardholder API](https://www.airwallex.com/docs/api#/Issuing/Cardholders/_api_v1_issuing_cardholders_create/post "Create Cardholder API") to determine which fields are required for your region.
2. Certain ID documents will require an image upload. Please refer to the [File Service API](https://www.airwallex.com/docs/api#/Supporting_Services/File_Service/Intro "File Service API") to perform this
3. For each new cardholder resource created, we require the `express_cardholder_consent`field to be passed. By setting this field to ‘yes’ you confirm that you have the express consent of this individual for Airwallex to verify their identity with Airwallex service providers and database owners in accordance with the [Identity Verification Terms](https://www.airwallex.com/terms/identity-verification-terms-au "Identity Verification Terms").


Creating Cardholders

Currency Based Controls

Merchant Based Controls

Transaction Based Controls

Time Based Controls

You can specify how and where the cards you issue may be used, these rules are called Authorisation Controls. Authorisation Controls are specified when a [new card is requested](https://www.airwallex.com/docs/api#/Issuing/Cards/_api_v1_issuing_cards_create/post "Create Card API") but can also be updated later on.

Airwallex Issuing offers the following types of Authorisation Controls:

1. Currency based controls
2. Merchant based controls
3. Transaction based controls
4. Time based controls


Control Management in WebApp

Authorisation Controls

These controls enable the ability to specify the activity range for a card upon creation using an ‘Active From’ and ‘Active To’ date.

- ‘active_from’: If provided, authorizations prior to this time will be rejected.

- ‘active_to’: If provided, authorizations after this time will be rejected.


Embedded fields integration - Subscription and Autodebit (MIT)

Enable your customers with recurring payment

Integration Options

Recurring Payments

Interact with Airwallex customers and services as a third-party provider

What is Airwallex Open Banking?

How does it work?

Overview

Starting with Airwallex Open Banking

Depending on the jurisdiction in which you operate, and the types of accounts you have with us, your Airwallex account will be assigned to either a __pre-funding__ or a __post-funding__ workflow. 

Your funding mode will dictate the timing both of when you fund Airwallex and when Airwallex will settle your conversions. If you are unsure of which funding mode you have been assigned, please contact your customer support representative, who would be happy to assist. 

### Pre-Funding Workflow

Prior to booking any conversion or payout, pre-funded clients must first top-up their Airwallex [wallet](https://help.airwallex.com/hc/en-gb/articles/900001756166-Funding-your-wallet). The funds required for a conversion or payout are deducted from the relevant wallet balance and cannot exceed your available funds in the currency you are converting or paying out from. 

![Pre-funding workflow](//images.ctfassets.net/c3n7jozh84hr/54aYZWHEtxiGCJNxSAy7E1/f1b780378aa4d966d86ede587fb7cd74/Pre-funding_workflow.png)

### Post-Funding Workflow

Post-funded clients are permitted to book conversions and payouts without sufficient funds available in their wallet. These accounts will have a limit assigned to them, which will be the upper limit of unfunded transactions you can have open with Airwallex at any one time. 

![Post-funding workflow](//images.ctfassets.net/c3n7jozh84hr/7sORc832YWNax2QAXnb5D3/ef434e5d2662c617c384218209c12685/Post-funding_workflow.png)

### Settlement Timing

When booking a conversion or payout with Airwallex, you will have the option to select the desired date for each transaction to settle. This “conversion date”, along with your funding mode, will determine when funds will be settled to and from your wallet. 

If you do not select a date, you will be assigned a “default date”. For pre-funded clients, the default date will always be same-day, for immediate settlement. For post-funded clients, the default date will depend on your available wallet balance in currency you are converting or paying out from at the time of booking. If funds are sufficient, the conversion date will default to same-day, immediate settlement. If funds are insufficient, the default date will return the next valid business day, accounting for any holidays in the currency you are funding Airwallex with.

![Settlement Timing](//images.ctfassets.net/c3n7jozh84hr/4drdnjgsY76Ts8czvv4OKs/1c16ea6165f49499e8cddf1caa64d409/Settlement_Timing.PNG)

For post-funded clients, if the wallet balance is insufficient at 9am on the conversion date, retry will be scheduled for every 30 minutes until funds have arrived.

The Airwallex location that you are onboarded with will determine your account time zone. Each Airwallex location has been assigned the following time zones: 

| AWX Entity     | Time Zone     | UTC     |
| ---------- | ---------- | ---------- |
| AWX HK       | Asia/Hong Kong       | UTC +8       |
| AWX AU       | Australia/Melbourne       | UTC +11       |
| AWX SG       | Asia/Singapore       | UTC +8       |
| AWX UK       | GMT       | UTC +1       |
| AWX JP       | Asia/Japan       | UTC +9       |
| AWX US       | America/Los Angeles       | UTC -8       |


Funding and Settlement Models

The capture step initiates the financial transfer from the funds you put on hold with the initial payment intent confirmation.This is a required step for Card payments (Credit or Debit Cards) or for any other payment method requiring a second step to capture funds. 



Not executing this step on time or note executing it at all means you will not receive any funds. If you do not want to worry about it you have the option to use the auto_capture parameter in your payment intent or to set it up by default in your account.


You need to follow the below process:

 1. Use the `POST/api/v1/pa/payment_intents/{id}/capture`, to request the capture of your payment. Upon successful completion the appropriate financial transactions will be generated and the payment intent will subsequently appear on your settlement report. You will receive a synchronous response to inform you the request has been taken into account.

```curl
curl -X POST \
  https://pci-api.airwallex.com/api/v1/pa/payment_intents/int_tkZsvKMHzf37yTFqlztZ5NYEAvD/capture \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer your_bearer_token' \
  -d '{
  "amount": 1, 
  "request_id": "285ecfc8-4c53-4543-8b9b-87d75e8666b9"
}'
```

```curl
{
    "id": "int_tkZsvKMHzf37yTFqlztZ5NYEAvD",
    "request_id": "285ecfc8-4c53-4543-8b9b-87d75e8666b9",
    "amount": 100.0,
    "currency": "HKD",
    "merchant_order_id": "d566b126-4e49-4233-93f4-b9ac809847db",
    "status": "SUCCEEDED",
    "captured_amount": 1.0,
    "latest_payment_attempt": {
        "id": "att_raOACk4zg17OZvmTzyFwKgOKWs",
        "amount": 100.0,
        "payment_method": {
            "id": "mtd_hq24SfHPX8Ft4d0T8tA3a905nYB",
            "type": "card",
            "card": {
                "expiry_month": "01",
                "expiry_year": "2023",
                "name": "Adam",
                "bin": "401200",
                "last4": "1003",
                "brand": "visa",
                "issuer_country_code": "RU",
                "card_type": "credit",
                "fingerprint": "Viy7U4n4UoLAcY9MVrdVqDFdXt0=",
                "cvc_check": "unknown",
                "avs_check": "unknown"
            },
            "status": "VERIFIED",
            "created_at": "2020-06-28T10:04:10+0000",
            "updated_at": "2020-06-28T10:04:10+0000"
        },
        "status": "CAPTURE_REQUIRED",
        "provider_original_response_code": "00",
        "authorization_code": "647902",
        "captured_amount": 1.0,
        "refunded_amount": 0,
        "created_at": "2020-06-28T10:04:10+0000",
        "updated_at": "2020-06-28T10:04:18+0000",
        "authentication_data": {
            "ds_data": {},
            "fraud_data": {
                "action": "ACCEPT",
                "score": "-1"
            },
            "avs_result": "U",
            "cvc_result": "U"
        }
    },
    "created_at": "2020-06-28T10:04:08+0000",
    "updated_at": "2020-06-28T10:04:14+0000"
}
```

We will also send you a notification in case the capture has failed or succeeded. Make sure to subscribe to it.


Capture

Accept Touch ‘n Go on your website by presenting your QR code to the shopper. 
![Touch 'n Go - desktop website browser](//images.ctfassets.net/c3n7jozh84hr/47aqGjA0bHlT4oYtcae72Z/ca949ddf63369532662ecbac63295e8e/image.png)

1. The shopper chooses to pay with Touch ‘n Go and is redirected to Touch ‘n Go cashier
2. The shopper uses Touch ‘n Go App to scan the QR code and completes the payment
3. Payment succeeds and the shopper is redirected back to the page you designated


Step 2. Redirect to Touch ‘n Go Cashier to complete payment

Accept Kakao Pay on your website by presenting your QR code to the shopper. See checkout experience as below
![Kakaopay - desktop website browser](//images.ctfassets.net/c3n7jozh84hr/2KnnCE6lFWJ8EPdhWshyuP/025c82a4c170d531ef377f09a84cc2dd/image.png)

1. The shopper chooses to pay with Kakao Pay and is redirected to Kakao Pay cashier
2. The shopper uses Kakao Pay App to scan the QR code and completes the payment
3. Payment succeeds and the shopper is redirected back to the page you designated


Step 2. Redirect to Kakao Pay Cashier to complete payment

Accept GCash on your website by redirecting your customer to GCash cashier.
![GCash - desktop website browser](//images.ctfassets.net/c3n7jozh84hr/281k5OC4axYBFIV3SJ7O3G/6c5317ff87bb3d549178f9562cb83a6f/image.png)

1. The shopper chooses to pay with GCash and is redirected to GCash login page
2. The shopper logs in to GCash account and completes payment
3. Payment succeeds and the shopper is redirected back to the page you designated


Accept AlipayHK on your website by presenting your QR code to the shopper. See checkout experience as below
![AlipayHK - desktop website browser](//images.ctfassets.net/c3n7jozh84hr/7pt0hwNr0r72WdKCqqhSTF/b85ee7cb125356776ba9c5201e2d15d4/image.png)

1. The shopper chooses to pay with AlipayHK and is redirected to AlipayHK cashier
2. The shopper uses AlipayHK App to scan the QR code and completes the payment
3. Payment succeeds and the shopper is redirected back to the page you designated


Step 2. Redirect to AlipayHK Cashier to complete payment

Accept Alipay on your website by presenting your QR code to the shopper. See checkout experience as below
![Alipay - desktop website browser](//images.ctfassets.net/c3n7jozh84hr/3kbJmv1hEvsfNIbjPggcVI/86521e7bff5595d1f4075b6b80ea5d6b/image.png)

1. The shopper chooses to pay with Alipay
2. The shopper is redirected to Alipay cashier
3. The shopper uses Alipay App to scan the QR code and completes the payment
4. Payment succeeds and the shopper is redirected back to the page you designated


Step 2a: Create and connect a connected account for businesses

Using the Scale API you can create Airwallex accounts for the users of your platform or marketplace. Below explains how you can onboard your users if they are individuals without a registered company entity.

There are three main steps to successfully onboard the individuals to Airwallex:

1. Determining and collecting the information/ data required
2. Creating the account
3. Submitting the account for activation

Additionally you need to consider cases where the activation requires additional measures:

4. Handling additional requirements during account activation


1. Determining and collecting the information/ data required

2. Creating the account

3. Submit the account for activation

4. Handling additional requirements during account activation

Step 2b: Create and connect a connected account for individuals

Website QR

WeChat Official Account

WeChat Mini Program 

Gain access to shoppers on WeChat

Choose the integration method that best suits your needs

Accept omni-channel payments from your shoppers with WeChat Pay

WeChat Pay

Payment

Payment with 3D secure

Management of payment credentials

Cancellation

Refund

Customs Declaration

Our native API integration allows you to handle 100% of the front-end and interactions between your front and backend. It is the most suitable if you are PCI-DSS compliant and want to leverage that capability to provide a customized check-out experience to your buyers.


Native API

The Airwallex Customs Declaration functionality enables Merchants who sell goods to mainland China via bonded warehouses to send payment information to China Customs conveniently and safely as regulated. 

Currently, this service supports custom declarations for WeChat Pay transactions that are completed within a year. 


To help you better understand what role Airwallex plays in your declaration process and what functionality our customs declaration API delivers, the Customs Declaration Model below illustrates the major parties in your overall declaration procedures. 
![Illustration - Customs Declaration](//images.ctfassets.net/c3n7jozh84hr/7CpqCUNchbrk2N1OIIbKBG/6f04ee36f9e3bccd43141cb06c495d93/Illustration_-_Customs_Declaration.png)

 1. The customer completes the purchase.

 2. You, as the merchant, shall send custom details and receives payment data via Airwallex Customs Declaration API (see guideline below).

 3. Same as your common practices of completing declaration, it is your responsibility to inform the logistics to send shipment details for declaration, with payment data attached. Also, you need to send order details for declaration, with payment data attached.

 4. After the customs receives all the required information, they will cross-check the detailed information of the order sent by you,  payment methods and logistics. If details matched, customs will agree the merchant to dispatch goods.


Guideline for Customs Declaration

Error handling

Airwallex uses conventional HTTP response codes to indicate the success or failure of an API request.


HTTP response codes

Error response structure

Error response examples

Error response examples for HTTP response code 400

Error codes for 401, 404

Error codes for 400

Error codes

Airwallex uses [versioning](https://www.airwallex.com/docs/api#/Versioning) to improve our API without affecting the existing users. In this chapter, the API examples as well as the notification event types are all presented in the latest version. For older versions, please refer to our [official API documentation](https://www.airwallex.com/docs/api).

__What’s the existing versions?__

 - 2020-04-30 (latest version)
 - 2019-09-09

__How do I choose the version?__

You may specify the version per API call by setting the __x-api-version__ header. However, in most cases you should rely on the configured version in your account. Overriding version by header is designed for testing and migrating to a new version. 

For webhook notification, you may only specify the expected event version during the webhook creation.


API Versioning

You can [retrieve all transactions](https://www.airwallex.com/docs/api#/Issuing/Transactions/_api_v1_issuing_transactions/get "Get transactions ") associated with an account or for a specific card and also [get one specific transaction by ID](https://www.airwallex.com/docs/api#/Issuing/Transactions/_api_v1_issuing_transactions__id_/get "Get single transaction").

View Transactions Via WebApp

View Transactions

Card management APIs allow you to manage your cards and associated transactions.


Card Cancellation

Card Details Update

Manage Cards

The card object is the resource associated with the card issued by Airwallex. It holds details such as linked accounts and card based spending restrictions and so on. The card object will also allow the client to specify who the card is for (themselves or other entities), card form (physical or virtual), and the number of uses (single or multiple).

To set up a card, use the [Create a card API](https://www.airwallex.com/docs/api#/Issuing/Cards/_api_v1_issuing_cards_create/post "Create Card API") which returns a `card_id`. You would then use this `card_id` to [get card details](https://www.airwallex.com/docs/api#/Issuing/Cards/_api_v1_issuing_cards__id_/get "Get card details").

__Please note:__

1. The Card Object request will not return the full PAN and CVV but will return a Card ID. To get the card details you will need to invoke a [Get sensitive card details](https://www.airwallex.com/docs/api#/Issuing/Cards/_api_v1_issuing_cards__id__details/get "Get sensitive card details") request with the relevant Card ID;
2. To find out the remaining limits for any card under your account, please invoke [Get card remaining limits](https://www.airwallex.com/docs/api#/Issuing/Cards/_api_v1_issuing_cards__id__limits/get "Get card remaining limit") with the relevant Card ID;
3. Issued cards are `Active` and can be used to transact straight away;
4. All Airwallex issued cards are linked to the client’s Airwallex account and funded balancers, so unlike a traditional prepaid product you don't have to lock-in funds on the card when requesting it.





Create a Card via WebApp

Create Cards

The Airwallex Issuing Platform can be used to implement an organization's own consumer cards proposition. By utilizing the Airwallew Bin and along with Airwallex’s Scale and Issuing products, a card can be provisioned for an organisation’s end customer. This card can be topped up via a dedicated collection account specific to that card / cardholder.

In addition, the balance can be extended to hold multiple currencies if required to support a specific use case.

The end customer can be programmatically onboarded including the full KYC process. Access to balance and transaction information is provided by an API enabling a fully native experience to be developed.

1. Via an organisation’s native experience, a card holder can sign up for a Card product providing the relevant proof of identification, and then be instantly provided with a Virtual Card. The physical card can be sent later in the post;
2. At the time of card creation, a unique collection bank account for a desired currency is created and provided to the card holder;
3. The cardholder is told about the card top up account and then move funds to that account;
4. Once funds are available the card can be used;
5. A full view of balance and transaction history is available;
6. Additionally the card can be provisioned to store multiple currencies at the same time either via top up from specific currency collection accounts or by utilizing Airwallex’s FX platform.


Whitelabel Cards

In the insurance industry, speed and control are critical to an end user experience. The Airwallex Issuing platform can be utilized to create this experience.

At the point where an insurance claim is approved, the Insurer can connect to the Airwallex Issuing platform and generate a single use or multi use Virtual card. This card can then be sent to the claimant via their mobile application.

The Virtual card can be locked down to a specific amount and merchant category.

The claimant can visit any service provider who can take card payments (Online or POS), provide the full card details and complete payment for services rendered. Metadata can be associated with cards so as to simplify reconciliation for the Insurer.

Due to Airwallex’s multi currency capabilities the same solution can be rolled in a single country or across a global insurers network.

1. A claim is approved by Insurance assessor in their system;
2. The insurance system requests a single  / multi use Virtual Card for the relevant amount, currency and merchant type via Airwallex API;
3. Airwallex instantly generates a Virtual Card and sends the PAN back to the system via an API response. Virtual Cards are sent out active to the claimant making the transaction process seamless;
4. Claimant uses the Virtual Card details to make a payment with the service provider;
5. Transaction reports are available to support automated reconciliation with the Insurers system.



Automated Insurance Payouts

In the gig economy, contracted staff (Gigster) are looking to be paid quickly, with the payment linked to a job being completed and not on a weekly or monthly cycle.

Utilising Airwallex’s Issuing Platform, a Virtual or Physical card can be generated for a new gigster with funds sent to the card programmatically and in real time when a job is completed. The gigster can then use the card to make payments straight away.

For global organisations funds can be dispersed in a single currency so as to simplify reconciliation activities, Airwallex’s multi currency card will then facilitate local transactions in the currency of the gigsters location.

1. When a gigster is onboarded to the orgsanitions platform they can be provided with a virtual card instantly (a Physical card can follow later in the post);
2. When a job is completed the organization will transfer funds from their master account to the gigster’s card;
3. The funds are available immediately for the gigster to make a payment;
4. Balance and transaction history is available via an API and can be integrated with the gigsters own app experience.


Gig Economy Payroll

Organisations typically have a variety of ongoing payment needs, with a number of payments to be made to suppliers based overseas. These businesses can leverage the Airwallex platform to acquire FX at near interbank rates and then issue cards to payout suppliers in various currencies. You can choose one virtual card for each supplier or for each cost-centre, and set up cards in a way that controls how much is spent and where the card is used.

The savings start when the FX is processed via Airwallex’s market leading FX engine allowing customers access to near interbank rates. When cards are used to payout these funds, there are no hidden fees or charges. 

For the organisations with recurring payment needs, for example monthly subscriptions payments for business software, memberships, recurring office expenses, you can manage your volume by leveraging the Airwallex platform.

1. Organisation requests a multi-use virtual card; sets the allowed currency along with associated transaction limits. The Organisation also nominates the relevant merchant category that is to be allowed, and provides the cost-centre number in the meta-data field;

2. A multi-use Virtual Visa card is generated instantly;

3. The Organisation provides the virtual card details to the supplier via the supplier’s website or platform integration (leveraging the supplier’s payment gateway);

4. As needed (on a recurring basis) the supplier’s gateway initiates a card not present transaction which is routed to Airwallex via the Visa network.






Recurring or Subscription Based Payments

Online Travel Agencies (OTAs) allow customers to book airline tickets, car rentals, hotel rooms and more through an easy to use online interface. Typically, an OTA collects payment from its customers and then makes a payment to the Hotel/Airline via a Global Distribution System (GDS) (such as Amedeus, Galileo).

OTAs (or the GDS nominated by them) can leverage Airwallex Issuing to request one-time use virtual cards through to make these payments. Cards can be set up for a specific amount and currency, along with additional controls such as an allowed merchant category code.

OTA signs up with Airwallex; sets up currency balances in all currencies they require payouts, such as USD, THB, SGD, HKD and so on. They then leverage the Airwallex platform to convert those currencies at near interbank rates.

1. OTA's Customer makes a booking and chooses to pay to the OTA directly (as opposed to the customers paying the hotel directly), the payment is collected from the customers;

2. OTA’s system requests a single use Virtual Card for the relevant amount, currency and merchant type via Airwallex API; 

3. Airwallex instantly generates a Virtual Card and sends the PAN back to the OTA’s system via an API response. Virtual Cards are sent out active to make the transaction process seamless for the OTAs;

4. OTA’s system uses the Virtual Card details to push out the reservation to the GDS;

5. The GDS pushes out the details to the relevant hotel’s property management system (PMS). The hotel's PMS saves card information along with reservation details;

6. When the customer checks out (completes their stay at the hotel), the hotel’s system uses the stored card to generate a transaction, which is routed to Airwallex via the Visa network;

7. Airwallex checks the OTA’s relevant currency account and if there’s sufficient balance in the relevant currency, the transaction is approved and the wallet debited.
![OTA Case study export](//images.ctfassets.net/c3n7jozh84hr/569dExK1l29UemASIgjLAH/bfd099feb094c17fd9c65178280ba999/OTA_Case_study_export.svg)



Online Travel Agencies

Airwallex’s Issuing platform enables businesses to create and manage multi-currency virtual prepaid and debit cards allowing you to unlock the power of the Visa network to pay millions of suppliers globally within seconds.

All Airwallex issued cards are multi-currency and allow you to transact in over 140 currencies supported by Visa, with no international transaction fees, we also offer multiple settlement currencies (Direct Billing).

Airwallex provides a set of RESTful APIs that allows your business to manage their card program. Cards are issued directly to clients to make business-to-business payments quickly, with ease and efficiency.

Airwallex Issuing capabilities support:

1. Provision of Visa prepaid and debit cards (Utilising Airwallex’s principal membership of Visa)
2. Single use or multi use virtual cards
3. Expense Cards (Card is associated with your business) or Employee Cards (Card is associated with a named individual who is a representative of your business) 
4. Creation of authorisation controls to control the usage of your cards
5. Usage of a single funding source for all cards or seperate sources for each card

As an Airwallex Issuing customer, you don't need to worry about BIN sponsorship, card production, transaction processing or balance management.

Airwallex is fully PCI compliant and depending on your requirements and certifications we can pass full or partial card details to you.


Direct Billing is offered by Airwallex in select G10 currencies (See [Supported Currencies](/issuing__supported-currencies)). For these currencies, we can directly debit your Airwallex multi currency account - No more hidden charges or conversion costs.

Important

These controls define where the cards may be used. Merchant restrictions can be based on the following levels:

- Merchant Category Code (MCC) – Specifies the MCC where the card can be used. An MCC is a unique identifier for a type of goods or services provided by a set of merchants.
- MCC Group (Coming soon) – Specifies the MCC where the card can be used. An MCC group is a unique identifier for a group of merchant category codes. These groups are provided by Airwallex
- Merchant ID (Coming soon) - Specifies exactly ‘which’ merchant the card can be used by/at

If the Merchant control object is empty then all merchant types are allowed.



These controls define for which transaction currencies can be processed. You have the option to select specific currencies to be allowed or to allow all currencies leaving the currency control object empty.



Customers can get a list of transactions associated with their account, requested via our API based on a number of parameters for example a specific card, date range, merchant category and so on.

### Sample Request
```curl
curl --request GET \
--url 'https://pci-api-demo.airwallex.com/api/v1/issuing/transactions?billing_currency=string&card_id=string&from_created_at=to_created_at%20-%2030%20day&page_num=0&page_size=100&retrieval_ref=string&to_created_at=current%20time&transaction_type=string' \
--header 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJ0b20iLCJyb2xlcyI6WyJ1c2VyIl0sImlhdCI6MTQ4ODQxNTI1NywiZXhwIjoxNDg4NDE1MjY3fQ.UHqau03y5kEk5lFbTp7J4a-U6LXsfxIVNEsux85hj-Q'
```

Customers can get a list of authorisations associated with their account, requested via our API based on a number of parameters for example a specific card, date range, merchant category and so on.

### Sample Request
```curl
curl --request GET \
--url 'https://pci-api-demo.airwallex.com/api/v1/issuing/authorizations?billing_currency=string&card_id=string&from_created_at=to_created_at%20-%2030%20day&page_num=0&page_size=100&retrieval_ref=string&status=PENDING&to_created_at=current%20time' \
--header 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJ0b20iLCJyb2xlcyI6WyJ1c2VyIl0sImlhdCI6MTQ4ODQxNTI1NywiZXhwIjoxNDg4NDE1MjY3fQ.UHqau03y5kEk5lFbTp7J4a-U6LXsfxIVNEsux85hj-Q'
```

View Authorisations

When an Airwallex issued card is used to make a purchase, an authorization request is initiated by the merchant which reaches Airwallex via the card scheme i.e. Visa and so on.

We will perform a number of checks to ensure that the authorization is genuine and meets any spend controls you had previously set up.

There are two scenarios in which an authorisation request can be received. If we receive a final transaction (called ‘Clearing’) from the merchant we will deduct the requested amount from your balance straight-away.

Sometimes we will receive a pre authorisation request first followed by what is called a ‘clearing’ advice later. In this scenario we will reserve funds with the initial request (These funds will be shown in your reserve balance) and the funds are only deduced fully when the final clearing advice is received. If the merchant does not send the clearing advice in a timely manner (10 days), it is reversed and the funds are released back to you.


Purchase Lifecycle

Airwallex issued cards are multi-currency and can be used for transactions in any currency supported by Visa, as long as you have sufficient balance in your Airwallex account to cover the transaction.
For a transaction in a currency we offer Direct Billing in, we will directly debit your Airwallex multi currency account in that currency without any further hidden charges or conversion fees. For example, for a GBP transaction, your GBP wallet will be debited.
For a transaction in all other currencies, we will debit an equivalent amount from your Base Currency wallet (AUD for Australia). In this case, the conversion rate we use will be based on Visa’s daily rate. For eg, for an AED transaction, your AUD wallet will be debited for an equivalent amount based on Visa's daily rate.



Direct Billing is offered by Airwallex in the following currencies
USD, AUD, CAD, SGD, NZD, HKD, JPY, EUR, GBP, CHF   

Supported Currencies

To make a purchase using Airwallex issued cards, you need to ensure your wallet balances have sufficient funds to use this card. If there are insufficient funds in the corresponding transaction balance then the transaction will be declined. 

You can add funds to the transaction currency balance by either adding funds in your local currency and converting to the transaction currency or adding funds directly to the transaction currency if you have them.


Funding

If clients have reasons to question a purchase made with an issued card, they can dispute it. Please contact your account manager or email support@airwallex.com. We will use the information you provide us and create a dispute request with Visa. The purchase amount is reversed while the dispute process takes place. If the dispute is upheld, this amount is credited back to your account.


Disputes

These controls allow you to specify spend controls on the card. All Transaction controls are set in a single currency with the transaction being converted to this control currency in realtime. You can select from a number of currencies to be used for Transaction Controls.

Transaction Controls can be:

- Per-transaction: Through this control, you can specify how much you want the card to allow for each transaction in a given currency. This control is especially useful when you set up single-use cards for specific payments
- Daily transaction: Through this control, you can specify the maximum card spend for each day
- Weekly transaction: Through this control, you can specify the maximum card spend for each week
- Monthly transaction: Through this control, you can specify the maximum card spend for each calendar month
- All time: Through this control, you can specify the maximum card spend during its valid period



Reviewing Remaining Spend

Transaction Control Behaviour

Contributing

Payment Acceptance enables new or existing Airwallex Merchants to directly collect money from your consumers through your webshop. Airwallex provides you with payment acceptance capabilities through its payment gateway and partner acquirers domestically in selected regions and for Buyers located anywhere in the globe.

Airwallex Payment Acceptance capabilities are integrated into Airwallex value chain providing you a single integration to get paid by your Buyers, settle the funds in the most suitable currency for you in the Airwallex balance and then repatriate the proceeds to your main country or even leverage those to pay your suppliers in other countries with our Issuance or Payout capability.

Create your Airwallex account by submitting your business information via the [online sign up](https://www.airwallex.com/app/signup?referral=Y29ycHNpdGU%3D) form or by [contacting us](https://www.airwallex.com/contact-sales) directly. Once your account is activated, you will immediately be able to start accepting payment through Airwallex API. We may contact you in case we need further information to complete the onboarding with our partner acquirers.

Take a look at the [Airwallex API](https://www.airwallex.com/docs/api#/) and find out which are the most suitable flows for you or take a look at the Product Acceptance Use Cases to learn how it can help you. Integration can begin immediately following registration success. One of our integration managers will be on hand to guide you through the process of integration, including resolving any queries and helping with testing.

Integrations

Markets and Payment methods 

Starting with Payments

Integration

Customize Usage

Set up Wechat Pay

Features

Examples

The Airwallex iOS SDK is a framework for integrating easy, fast and secure payments inside your app with Airwallex. It provides simple functions to send sensitive credit card data directly to Airwallex, it also provides a powerful, customizable interface for collecting user payment details.

Get started with our integration guide and example project.


Features	DANA
Merchant supported countries/regions	HK
One-off payment	✅
One-off payment with 3DS	⛔
Recurring Payment	✅
Refunds	✅
Partial Refunds	✅
Disputes/Chargeback	✅