Conversion statuses (legacy API versions)

Error codes (legacy API versions)

Conversion variations (legacy API versions)

Conversion webhooks (legacy API versions)

Conversions

A quick introduction to building with Airwallex APIs

Quickstart

Explore our comprehensive reference to integrate with Airwallex API endpoints

API Reference

Learn how to receive push notifications via webhooks

Webhooks

This page applies for __API version 2024-06-14 or earlier__.

Conversions have different status types and state transitions. There are two types of status: Intermediate (transition) and Terminal (final).

![FX legacy status](//images.ctfassets.net/c3n7jozh84hr/4YNKeKmV143eX4cIVN7fAb/afe1ebcca7c165b804e6ba98d39e066a/image.png)


| STATUS     | DESCRIPTION     | EMITTED WEBHOOK    | NEXT STEPS     |
| ---------- | ---------- | ---------- | ---------- |
| `AWAITING_FUNDS`       | Intermediate status. Conversion booked successfully, and waiting for client funds. Post-fund pending deduction state.       | `conversion.awaiting_funds`       | On the settlement date, if there are sufficient funds in sell currency, the conversion will transition to `PENDING_SETTLEMENT` and then be immediately `SETTLED`.
You can cancel (`CANCELLED`) unsettled conversions using the [Create an amendment](/api#/Transactional_FX/Conversion_Amendments/_api_v1_fx_conversion_amendments_create/post) API . See [Funding and settlement models](/transactional-fx__funding-and-settlement-models) for more information.       |
| `PENDING_SETTLEMENT`      | Intermediate status. Conversion is processing. Pre-fund future-dated conversions pending settlement state.       | `conversion.pending_settlement`	       | On the settlement date, the conversion will transition to `SETTLED`. You can cancel (`CANCELLED`) unsettled conversions using the [Create an amendment](/api#/Transactional_FX/Conversion_Amendments/_api_v1_fx_conversion_amendments_create/post) API. See [Funding and settlement models](/transactional-fx__funding-and-settlement-models) for more information.      |
| `CANCELLED`       | Terminal status. Conversion cancelled. Funds returned to client wallet.	| `conversion.cancelled`       | No action needed.    |
| `SETTLED`       | Terminal status. Funds have been settled in the wallet.	       | `conversion.settled`       | No action needed.       |
| `ROLLOVER_REQUESTED`       | Deprecated       | `conversion.rollover_requested`       | N/A       |
| `PENDING_ROLLOVER`       | Deprecated       | `conversion.pending_rollover`       | N/A       |

This page lists all the possible errors associated with the HTTP 400 status code while creating/managing conversions and conversion amendments via our API endpoints.

For 400 errors, the response you receive will contain a `code` specifying the error encountered, `message` about the error, and `source` providing additional context about the error.

## General errors with example response

A general error provides an error response with `code`, `message`, `source`. Like in the example below, the response contains an errors object with:
- `code`: Unique numeric identifier of the specific validation error encountered.
- `message`: A message about the specific error encountered.
- `source`: The specific field or object within the request that has failed.
- `details`: Additional details about the request. Generally includes error code trace ID (`correlation_id`) for Airwallex debugging.

__Example:__
```json
{
   "code": "amount_above_limit",
   "message": "Buy amount above the limit of USD 5000000 equivalent",
   "source": "buyCurrency"
}
```

__Example with details:__
```json
{
   "code": "account_not_authorized",
   "details": [
       {
           "code": "correlation_id",
           "message": "26eebb32-36a8-4764-a2af-9621426b1aa4"
       }
   ],
   "message": "account not authorised [POST_TX_CREATION]",
   "source": "account"
}
```

See below for all potential error codes and descriptions, organized by corresponding [Conversion](/api#/Transactional_FX/Conversion/Intro) & [Conversion Amendments](/api#/Transactional_FX/Conversion_Amendments/Intro)  endpoints.

Conversion errors

MarketFX and LockFX errors

Conversion amendments errors

Conversion variations only apply to __LockFX__.

You can apply the following conversion variations to your account to strike the right balance between __cost__, __speed__ and __matching of commercial workflows__ to the pricing and execution flow selected. Contact your Airwallex Account Manager to add/update any of these variations to your account. 

Quote validity period

Quote usage

| Web app Label                     | Event Type                     | Description                                                   |
| -------------------------------- | ------------------------------ | ------------------------------------------------------------- |
| Conversion -> Awaiting funds     | conversion.awaiting\_funds     | Conversion booked successfully, and waiting for client funds. |
| Conversion -> Pending settlement | conversion.pending\_settlement | Conversion is processing                                      |
| Conversion -> Settled            | conversion.settled             | Funds have been settled in the wallet.                        |
| Conversion -> Pending rollover   | conversion.pending\_rollover   | Conversion is pending for rollover.                           |
| Conversion -> Rollover requested | conversion.rollover\_requested | Conversion is requested for rollover.                         |
| Conversion -> Cancelled          | conversion.cancelled           | Conversion cancelled.  Funds returned to client wallet.       |

As we continue to improve our Conversions product, we highly recommend that you integrate to the __latest API version__ to enjoy our new features and capabilities.

Starting from __API version 2024-06-30__, we have released major upgrades which introduced a new set of Conversion status definitions and transitioning experience. For the behaviours on __older versions (2024-06-14 or earlier)__, please refer to the subpages under this section.

You can also refer to our [API reference](/api#/Transactional_FX/Conversion) for the full technical documentations of all historical API versions.

docsLogo

iOS SDK

Android SDK

Registered user checkout

Install the Airwallex Google Pay Payments App

Getting Started

Install Airwallex Card Payments app

Install Airwallex Online Payments App

Install Airwallex Klarna Payments App

Install Airwallex Afterpay Payments App

Install the Airwallex Apple Pay Payments App

Shopline

Supported currencies

 Micro-deposit verification

Transfer webhooks (older versions)

Desktop/Mobile Website Browser - Afterpay / Clearpay

Afterpay / Clearpay

Pakistan

Bangladesh

Indonesia

Market & infrastructure coverage

Settlement report

Transaction & fee types

Payment activity export

Payments rounding logic

Reporting

Enable Native Credit/Debit Cards

Hungary

Zambia

Wallis and Futuna

Virgin Islands (British)

Viet Nam

Vanuatu

Uzbekistan

Uruguay

United States

United Kingdom

United Arab Emirates

Ukraine

Uganda

Turkey

Tunisia

Togo

Timor-Leste

Thailand

Tanzania, United Republic of

Tajikistan

Taiwan (China)

Switzerland

Sweden

Sri Lanka

Spain

South Africa

Slovenia

Slovakia

Singapore

Seychelles

Serbia

Senegal

Saudi Arabia

San Marino

Saint Pierre and Miquelon

Saint Martin (French part)

Saint Lucia

Saint Barthélemy

Rwanda

Romania

Réunion

Republic of the Congo

Qatar

Puerto Rico

Portugal

Poland

Philippines

Peru

Paraguay

Panama

Palestine, State of

Oman

Norway

Nigeria

Niger

New Zealand

New Caledonia

Netherlands

Nepal

Namibia

Morocco

Montenegro

Albania

Algeria

Andorra

Angola

Anguilla

Antigua and Barbuda

Argentina

Armenia

Aruba

Australia

Austria

Azerbaijan

Bahrain

Belgium

Belize

Benin

Bolivia

Bosnia and Herzegovina

Botswana

Brazil

Bulgaria

Burkina Faso

Cambodia

Cameroon

Canada

Canary Islands

Central African Republic

Chad

Chile

China

Colombia

Costa Rica

Côte d'Ivoire

Croatia

Curaçao

Cyprus

Czech Republic

Denmark

Dominican Republic

Dominica

Ecuador

Egypt

El Salvador

Equatorial Guinea

Estonia

Faroe Islands

Fiji

Finland

France

French Guiana

French Polynesia

French Southern Territories

Gabon

Gambia

Georgia

Germany

Gibraltar

Greece

Greenland

Grenada

Guatemala

Guernsey

Guinea-Bissau

Guyana

Honduras

Hong Kong SAR

Iceland

India

Ireland

Isle of Man

Israel

Italy

Jamaica

Japan

Jersey

Jordan

Kazakhstan

Kenya

Korea, Republic of

Kosovo

Kuwait

Kyrgyzstan

Latvia

Lesotho

Liechtenstein

Lithuania

Luxembourg

Macedonia, the former Yugoslav Republic of

Payout network