Last updated: 20 June 2025

API DEVELOPER TERMS & CONDITIONS

1. INTRODUCTION

1.1. By registering and using the Airwallex Platform, the Developer agrees to be bound by these API Terms & Conditions (the “API Terms”).

1.2. These API Terms, together with any other applicable Airwallex terms, collectively form a legal agreement between you (the “Developer”) and Airwallex which governs our provision of the Airwallex Platform.

2. ACCESS TO THE AIRWALLEX PLATFORM 

2.1. During the Term of these API Terms, Airwallex may grant the Developer access to Airwallex’s OAuthentication mechanisms (“OAuth”), application programming interfaces (“APIs”), software development kits (“SDKs”), app keys and access tokens, as well as Airwallex’s developer webpages and Documentation (collectively, the “Airwallex Platform”). 

2.2. The Airwallex Platform is designed to allow Developers to incorporate their applications, products and services with Airwallex’s global payments system (“Airwallex Services”), via integrations built into the Airwallex Platform (the “Integration”). 

2.3. If the Developer is providing application development services for, or is otherwise acting on behalf of a Mutual Customer (the “End User”) that will receive or otherwise benefit from any data, content or information, the Developer warrants and represents that:

(a) it is acting on an instruction of the End User;

(b) it is authorised to act on behalf of the End User, evidence of which the Developer agrees to provide to us if requested;

(c) the End User has acknowledged and agreed to be bound by Airwallex’s Third Party Application Terms, as may be amended from time to time;

(d) its agreement with the End User must not be inconsistent with these API Terms or any other agreement as between the End User and Airwallex or any agreement between Developer and Airwallex, as amended from time to time; and

(e) it will procure that any third party subcontractor the Developer uses complies with these API Terms. 

2.4. Each Party agrees not to, nor permit any third party to:

(a) submit any viruses, worms, defects, Trojan horses, malware or similar items;

(b) try to exceed or circumvent any security measures or technical limitations;

(c) copy, reverse-engineer, or otherwise modify the other Party’s Materials, access credentials, or such other Party’s website or content;

(d) download, scrape, post or transmit any part of the other Party’s website or content;

(e) use the other Party’s Materials in any manner that violates any Applicable Laws or any right of any person, including but not limited to any IP Rights or rights of privacy;

(f) engage in any activity that interferes with, disrupts, or accesses in an unauthorized manner the other Party’s services or the other Party’s platform, servers, or systems;

(g) make any statements that any of that Party’s platform is “certified” or otherwise endorsed, or that its performance is guaranteed, by the other Party; 

(h) sublicense the other Party’s Materials for use by a third party without prior consent;

(i) use, share, hold or sell Account Data for any purpose other than to relaying instructions via the Integration; or

(j) access the other Party’s platform for competitive purposes or publicly disseminate performance information or analysis relating to the other Party’s APIs.

2.5. The Airwallex Platform is provided “as is” and “as available” without warranties or representations of any kind. Airwallex does not warrant or guarantee that the:

(a) the Airwallex Platform or Airwallex Materials will be reliable, accurate, up to date or complete; or

(b) the Airwallex Platform will be available, ongoing, uninterrupted or error-free. 

Developer is solely responsible for its use of the Airwallex Platform and any data or content that it uses or shares with the Airwallex Platform. The Developer may have other statutory rights, in which case the disclaimers above will apply to the full extent permitted by law.

2.6. Airwallex is not obligated to provide support, maintenance, updates, upgrades, modifications or new releases of the Airwallex Platform (“Updates”). The Developer agrees to implement any Update within a reasonable time, as specified by Airwallex, and in any case no longer than six (6) months of Airwallex issuing the Update. Airwallex may also in its discretion impose additional eligibility requirements or restrictions for access to the Airwallex Platform or discontinue certain applications or services provided through the Airwallex Platform.

3. USING THE API

3.1. Subject to these API Terms, the Developer must: 

(a) use the Airwallex Platform solely to enable the Developer to access or interface with the Airwallex Service in accordance with these API Terms; 

(b) use the Airwallex Platform in a manner consistent with the Documentation or as Airwallex has otherwise notified the Developer, in writing, from time to time; 

(c) ensure any Account Data is collected, processed, transmitted, maintained and used in accordance with Applicable Laws; 

(d) take reasonable measures that protect the privacy and security of the Account Data and Airwallex Materials; 

(e) if providing application development services as described in Clause 2.3: 

i. only transfer Account Data to the End User in connection with the Airwallex Platform or as allowed under these API Terms; 

ii. where an End User submits a request that the Parties activate or terminate the Integration, Developer must take all required steps to assist Airwallex to activate or terminate the link in accordance with that request; 

(f) if generating access tokens when establishing the Integration or when relaying instructions via the Integration; 

i. encrypt such tokens; 

ii. take all steps and do all things reasonably necessary, prudent or desirable in order to protect and safeguard such tokens, including but not limited to adhering to Airwallex's prohibition on sharing, transferring, or otherwise distributing such tokens to any other person or entity without Airwallex’s prior written authorization, in no event with less than a reasonable degree of care; 

iii. notify Airwallex promptly upon discovery of any suspected or actual unauthorised access, use or disclosure of a token, and must take all reasonable steps, at its own expense, necessary to prevent or stop the suspected or actual breach; and

iv. revoke and permanently delete such tokens when Developer no longer requires access to the link for which the token was granted. 

3.2. Subject to these API Terms, the Developer must not: 

(a) develop any Integrations or associated services that are in contravention of any other agreements between Airwallex and the Developer; or

(b) exceed any Airwallex API limits set out in the developer webpages and Documentation.

3.3. The Developer acknowledges that its use of the Integration may be subject to certain usage limits and rate limits as determined and enforced by Airwallex in its sole discretion from time to time. These limits may include, but are not limited to, restrictions on the number of API calls the Developer can make within a specified time period (e.g., per minute, per hour, per day), the amount of data the Developer can transfer (upload or download) through the Integration, the number of concurrent requests the Developer can make, or the usage of specific API resources. If the Developer exceeds the limits, Airwallex may throttle Integration requests, or suspend the Integration.

4. INFORMATION AND MONITORING RIGHTS

4.1. Exchange of information

In order for a Party to perform the Integration, satisfy its obligations under this Agreement or to comply with any relevant requirements under the Applicable Laws, if reasonably requested by such Party, the other Party shall cooperate and share any relevant records and information with the requesting Party from time to time. 

4.2. Monitoring

The Developer shall enable Airwallex to monitor the Developer’s performance under these API Terms on an ongoing basis.

4.3. Security incident reporting

The Developer shall notify Airwallex immediately in the event of any security incident and in any event no later than 72 hours of becoming aware of the incident.

4.4. Service failure reporting 

The Developer shall promptly notify Airwallex in writing if an event occurs that may have a material impact on Developer’s ability to: 

(a) effectively maintain the Integration; or 

(b) comply with the Applicable Laws.

5. UNDERTAKINGS OF DEVELOPER

5.1. The Developer undertakes, warrants and represents on an ongoing basis that it has the right, power and authority to enter into these API Terms and to perform its obligations.

5.2. The Developer shall, at its own cost:

(a) perform its obligations in a professional manner and in accordance with these API Terms, the Documentation and any standards appropriate for its industry; 

(b) comply with Applicable Laws and maintain necessary licences, authorisations, approvals and consents in connection with these API Terms;

(c) not hold itself out as providing any licensable or regulated services to the End Users without Airwallex’s prior written consent;

(d) cooperate with Airwallex in the event of an investigation, inspection or request by a Regulatory Body, including any persons appointed by such Regulatory Body; and

(e) grant Airwallex access to all data that Airwallex reasonably requests pertaining to the      Integration and these API Terms, and shall have arrangements in place to ensure that Airwallex continues to have access to such data in the event that (i) Developer experiences insolvency, bankruptcy, enters into administration, or any other event that has or is reasonably likely to have a material adverse effect on their financial condition or (ii) there is a disruption in the business operations of Developer.

6. DATA PRIVACY, INFORMATION SECURITY & CONFIDENTIALITY

Data Privacy 

6.1. Each Party must ensure there is a legal basis under Applicable Laws for the collection, use, disclosure and transfer of Account Data to enable the Integration. 

6.2. Each Party must ensure that it obtains any relevant consent, in compliance with Applicable Laws, prior to collecting and transferring Account Data (including End User Account Data) to the other Party. 

6.3. Each Party will take all reasonable endeavours to ensure that the Account Data is protected against misuse and loss, or unauthorised access, modification or disclosure and will promptly notify the other Party of any loss of, or any unauthorised disclosure of or access to, the Account Data. 

6.4. Each Party may retain records in accordance with the Airwallex Privacy Policy and for compliance with Applicable Laws and internal compliance requirements.

6.5. Airwallex and the Developer (or if the Developer is providing application development services for, or is otherwise acting on behalf of an End User, then the End User instead of the Developer) are independent data controllers (each a “Controller”). Each Controller agrees to comply with its respective obligations under applicable Data Protection Laws.  

6.6. Each Party may only transfer Account Data between jurisdictions only where it has taken appropriate measures to ensure the transfer is lawful under Applicable Laws.

Information Security 

6.7. At all times, each Party must ensure appropriate technical and organisational security measures are in place to protect Account Data under its control. Each Party shall ensure that Account Data will only be accessed by its authorized employees, whose access shall be limited to those with a need-to-know based on their job responsibilities.  

6.8. Each Party agrees to meet all data security standards, as required by Applicable Laws or Regulatory Body, and any card network or payment method rules, including setting access restrictions and strict password requirements. 

6.9. The Developer will promptly notify Airwallex if Account Data is misappropriated, accessed or disclosed without permission (“Data Incident”), but in any event within 36 hours of becoming aware of such an event. The Developer will provide such information and assistance in respect of the Data Incident to Airwallex as reasonably required. 

Confidentiality

6.10. Each Party acknowledges that it will have access to Confidential Information belonging to the other Party.

6.11. Each Party further agrees that it will:

(a) not use Confidential Information in any way except as expressly permitted by, or as required to perform its obligations under these API Terms; 

(b) not disclose any of the other Party’s Confidential Information to any third party except as required: 

i. by law or any authority of competent jurisdiction; 

ii. to its agents, representatives and employees who ‘need to know’ such information in connection with these API Terms and agree to act in accordance with the terms and conditions of this Clause 6; 

iii. to that Party’s attorneys, accountants and other advisors as reasonably necessary; or 

iv. for the purposes of defending itself in relation to proceedings; 

(c) take reasonable precautions to protect the confidentiality of such information, at least as stringent as those taken to protect its own Confidential Information.

6.12. Each Party will remain liable for any disclosure of Confidential Information by its agents, representatives and employees, as well as the End User, as if it had made such disclosure.

6.13. In each of the exceptions set out in paragraph 6.11(b), the Developer shall give Airwallex reasonable formal written notice (provided that this is not in contravention of Applicable Laws) prior to such disclosure. 

6.14. The Parties agree that Clauses 6.10-6.14 will survive any expiration or termination of these API Terms.

7. LIABILITY 

7.1. To the maximum extent permitted under Applicable Law, the Parties will not be liable under any theory of tort, contract, strict liability or other legal or equitable theory for: 

(a) any lost profits (whether direct or indirect) or goodwill; or

(b) any indirect, incidental, special, consequential or exemplary loss or punitive damages, each of which is excluded by agreement of the Parties regardless of whether such losses and/or damages were foreseeable or whether such Party has been advised of the possibility of such damages.

7.2. To the maximum extent permitted by Applicable Laws, Airwallex’s liability to Developer in relation to these API Terms, whether in contract, negligence, liability, tort or other legal or equitable theory, for losses or damages shall not exceed USD $1,000 (or local currency equivalent).

7.3. For the avoidance of doubt, nothing in these API Terms shall be deemed to exclude, restrict or limit liability of either party (or their respective agents or subcontractors) for death or personal injury resulting from their negligence or any liability for fraudulent misrepresentation.

8. INDEMNIFICATION

8.1. The Developer is solely responsible for its use of the Airwallex Platform and any data or content that the Developer uses with the Airwallex Platform.

8.2. Developer shall indemnify and shall hold Airwallex harmless against all fines, damages, expenses and/or all related costs (including reasonably incurred legal costs) which arise from or are incurred by reason of: 

(a) breach by Developer of its obligations under these API Terms or use of the Airwallex Platform, including the Documentation;

(b) use of the Integration and the relationships or interactions of the Developer with any third party distributors of the Integration; 

(c) the intellectual property licensed to Airwallex by the Developer under these API Terms infringes the copyright of a third party; and 

(d) the wilful misconduct of any employee of Developer in connection with the obligations contingent upon either Party under these API Terms. 

9. INTELLECTUAL PROPERTY RIGHTS

9.1. No transfer

Except as expressly set out in these API Terms, nothing in these API Terms transfers any interest or otherwise affects the ownership of any IP Rights of either Party in any material, data, work, item, process or thing.

The Developer acknowledges that nothing in these API Terms will be construed as restricting or preventing Airwallex from independently creating (or receiving from third parties) features, applications, content, or other products or services that may be similar to or competitive with the Developer’s services. 

9.2. Integration 

The Developer retains ownership of any newly formed IP Rights developed in building the Integration, subject to Airwallex’s rights in any underlying Materials. The Developer agrees to provide Airwallex with a reasonable number of copies of or access to the Integration. 

9.3. Publicity 

Airwallex may publicly refer to the Developer as a user of the Airwallex Platform. Airwallex may also publish the Developer’s Marks (with or without a link to the Developer’s website or content) on our websites, in press releases, and in promotional materials without your prior consent. 

The Developer must first obtain Airwallex’s express written consent before it publishes Airwallex’s Marks, including on the Developer’s websites, application or in promotional materials. 

9.4. Licence

Each Party grants the other a revocable, non-exclusive, non-transferable, non-sublicensable, royalty-free licence to use any IP Rights in the other Party’s materials to perform its obligations under these API Terms, including: 

(a) to use, perform, and display the Integration on the Airwallex Platform; 

(b) for internal testing purposes (such as security testing); 

(c) to market, demonstrate and make the Integration available to End Users. 

Following the termination of these API Terms and upon written request from the Developer, Airwallex will make commercially reasonable efforts, as determined in its sole discretion, to remove references to the Integration from Airwallex’s website and Airwallex Services.

10. TERM AND TERMINATION

10.1. Term of the Agreement

The term of these API Terms shall commence upon the Developer’s acceptance of the terms herein and shall continue until terminated in accordance  with this Clause 10 or otherwise validly terminated, including if required by Applicable Laws (the “Term”).

10.2. Termination 

The Developer may terminate these API Terms at any time by ceasing all use of the Developer platform, servers, or systems and notifying Airwallex. 

Airwallex may terminate these API Terms for any reason upon providing 10 days notice to the Developer. In addition, Airwallex may suspend or terminate these API Terms immediately if, Airwallex reasonably determine that: 

(a) the Developer has violated these API Terms or any Documentation; 

(b) the use of the Integration is not in our or the End Users best interests; 

(c) Airwallex can no longer offer the Airwallex Platform; or 

(d) it is required by Applicable Laws, including instructions of Regulatory Body.

11. MISCELLANEOUS

11.1. Third Party Application Terms 

Any agreement in place between the Developer and an End User should not be inconsistent with Airwallex’s Third Party Application Terms, as amended from time to time. In the case of any inconsistency, Airwallex’s Third Party Application Terms shall prevail. 

11.2. Relationship

Nothing in these API Terms will be construed as creating a joint venture, partnership, agency, fiduciary or employment relationship among or between the Parties.

11.3. Assignment

Neither these API Terms nor any of the rights, interests or obligations under it may be assigned by a Party without the prior written consent of the other Party (which consent will not be unreasonably withheld or delayed), except:

(a) Airwallex may, without Developer’s consent, assign and transfer any of its rights and obligations under these API Terms, to any company within the Airwallex Corporate Group; and 

(b) Developer may, with Airwallex’s consent, which Airwallex will not unreasonably withhold, assign and transfer any of its rights and obligations under these API Terms, to any company within the Developer’s Corporate Group. 

11.4. Severability

If any provision of these API Terms is determined to be invalid or unenforceable by a court of law, the remaining provisions of these API Terms will remain in full force and effect.

11.5. Amendment

Airwallex may modify these API Terms or any additional terms that apply to the Airwallex Platform from time to time.

Changes specific to new services or features for the Airwallex Platform, changes made for legal reasons, and any changes to our Documentation or referenced policies will be effective immediately.

The Developer will be notified of changes to these API Terms that Airwallex believe are not adverse to the Developer’s interests no later than the day the change occurs. Otherwise, Airwallex will provide the Developer with 30 days prior notice.

The Developer agrees that its continued use of the Airwallex Platform after the changes become effective, constitutes acceptance of the modified terms.

11.6. Force Majeure

If either Party is delayed or hindered or prevented from performing any act required by reason of force majeure events, including significant currency fluctuations, strikes, lock-outs, employment troubles, inability to procure materials or services, failure of power, riots, insurrection, war, mud-slide, fire, earthquake, tsunami, or other similar reasons of a like nature not the fault of the Party delayed in performing work or doing acts required under these API Terms, the affected Party shall immediately provide notice to the other Party of such delay, and performance of such act shall be excused for the period of the delay and the period for the performance of any such act shall be extended for a period equivalent to the period of the delay.

11.7. Governing law 

For disputes arising between the Parties, these API Terms shall be governed by the laws of their applicable jurisdiction, without reference to its conflicts or choice of laws provisions. Each Party hereby consents to the non-exclusive jurisdiction of the courts of the relevant jurisdiction. 

Dispute resolution

The Parties shall make good faith efforts to resolve any dispute arising under these API Terms within thirty (30) days from the date on which a Party notifies the other Party that a dispute has arisen, and each Party shall refrain during that time (except for requests for injunctive relief) from initiating any litigation or other proceeding relating to such dispute. 

11.8. Financial or Credit Services

If the Developer uses the Airwallex Platform and provides a financial service or product (as described in Airwallex’s Acceptable Use Policy), the Developer is prohibited from using the Airwallex Platform without Airwallex’s prior written consent (“Airwallex Approval”). Further, the Developer represents, warrants and covenants on a continuing basis that the Developer:

(a) has obtained Airwallex Approval for each use case relating to the Developer’s Services;

(b) use of the Airwallex Platform would not result in any contravention by either party of any financial services licensing requirements or Applicable Laws; 

(c) will not use the Airwallex Platform for generating a lead for another financial service provider, for populating, informing, or distributing enquiries or applications for another financial services provider;

(d) will not act as an aggregator/distributor of above mentioned leads, enquiries, or applications populated with Data or in any other way facilitated by the Integration;

(e) will not imply, directly or otherwise, that Airwallex endorses, underwrites, brokers or makes any warranties or commitments around financial services;

(f) will comply with Applicable Laws pertaining to the provision of financial services; and

(g) will immediately notify Airwallex of any additional intended financial services use cases for the Developer’s Service, and obtain Airwallex Approval for those new use cases prior to implementing them. For the avoidance of doubt, Airwallex Approvals extend only to the use cases specified at the time Airwallex Approval is obtained.

12. DEFINITIONS AND INTERPRETATION

12.1. Definitions

In these API Terms, the following definitions shall apply: