Airwallex Payment Intents API

The Payment Intents API from Airwallex — 5 operation(s) for payment intents.

Documentation GitHub OpenAPI

Operations 5

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /api/v1/payment_intents/create Start a new payment · Create a payment intent #

Ask an LLM

“How do I start collecting a payment from a customer in Airwallex?”

“Can I create a payment intent before the shopper enters card details?”

Tell an agent

Create a new payment intent for an order.

Start a new payment so the customer can check out.

GET /api/v1/payment_intents/{id} Check a payment's status · Retrieve payment intent #

Ask an LLM

“Did a particular payment succeed or is it still pending?”

“Can I look up the current state of a payment intent?”

Tell an agent

Show me payment intent {id}.

Tell me the current status of payment {id}.

POST /api/v1/payment_intents/{id}/confirm Confirm a payment · Confirm payment intent #

Ask an LLM

“How do I confirm a payment intent so the charge goes through?”

“Can I submit a pending payment for processing once the customer is ready?”

Tell an agent

Confirm payment intent {id}.

Submit payment {id} for processing now.

POST /api/v1/payment_intents/{id}/capture Capture an authorized payment · Capture payment intent #

Ask an LLM

“Can I collect funds on a payment that was only authorized?”

“When should I capture a payment after the order ships?”

Tell an agent

Capture the authorized funds on payment {id}.

Collect the money for payment intent {id} now that the order has shipped.

POST /api/v1/payment_intents/{id}/cancel Cancel a payment · Cancel payment intent #

Ask an LLM

“Can I cancel a payment that has not been completed yet?”

“What happens if I cancel a payment intent the customer abandoned?”

Tell an agent destructive · confirm first

Cancel payment intent {id}.

Void payment {id} because the customer abandoned the order.

Specifications

⚙

OpenAPI

https://raw.githubusercontent.com/api-evangelist/airwallex/refs/heads/main/openapi/airwallex-payment-intents-api-openapi.yml

Other Resources

🔗

Overlay

https://raw.githubusercontent.com/api-evangelist/airwallex/refs/heads/main/overlays/airwallex-payment-intents-api-overlay.yaml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/airwallex:airwallex-payment-intents-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Airwallex Open Payment Intents API
  version: v1
  description: 'Best-effort OpenAPI 3.1 representation of the Airwallex REST API derived from

    https://www.airwallex.com/docs/api. Airwallex is a global payments and

    financial infrastructure platform. Coverage in this best-effort spec

    focuses on the Payment Acceptance and related core resources: payment

    intents, customers, refunds, payouts, transfers, balances, beneficiaries

    and account authentication. Endpoints accept and return JSON.'
  contact:
    name: Airwallex
    url: https://www.airwallex.com/docs/api
servers:
- url: https://api.airwallex.com
  description: Airwallex production
- url: https://api-demo.airwallex.com
  description: Airwallex demo / sandbox
security:
- BearerAuth: []
- ClientIdHeader: []
  ApiKeyHeader: []
tags:
- name: Payment Intents
paths:
  /api/v1/payment_intents/create:
    post:
      tags:
      - Payment Intents
      summary: Create a payment intent
      operationId: createPaymentIntent
      responses:
        '201':
          description: Created
  /api/v1/payment_intents/{id}:
    get:
      tags:
      - Payment Intents
      summary: Retrieve payment intent
      operationId: getPaymentIntent
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: OK
  /api/v1/payment_intents/{id}/confirm:
    post:
      tags:
      - Payment Intents
      summary: Confirm payment intent
      operationId: confirmPaymentIntent
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: OK
  /api/v1/payment_intents/{id}/capture:
    post:
      tags:
      - Payment Intents
      summary: Capture payment intent
      operationId: capturePaymentIntent
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: OK
  /api/v1/payment_intents/{id}/cancel:
    post:
      tags:
      - Payment Intents
      summary: Cancel payment intent
      operationId: cancelPaymentIntent
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: OK
components:
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: 'Bearer access token obtained via POST /api/v1/authentication/login using

        `x-client-id` and `x-api-key` request headers.

        '
    ClientIdHeader:
      type: apiKey
      in: header
      name: x-client-id
    ApiKeyHeader:
      type: apiKey
      in: header
      name: x-api-key