How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Airtm Payments / Payouts API

## OverviewThe Payouts endpoint enables your organization to send payments to recipients worldwide through the Airtm platform. This powerful endpoint supports both individual and bulk payment processing, making it ideal for paying employees, contractors, freelancers, vendors, or any other recipients who have Airtm accounts.## What are Payouts?Payouts represent outgoing payments from your enterprise account to recipient users. The payout process is designed to be flexible, secure, and reliable, with multiple options for creating and managing payments based on your specific needs.### Key Features- **Two-Step or One-Step Processing** - Choose your preferred workflow- **Real-Time Status Tracking** - Monitor payment progress instantly- **Comprehensive Recipient Management** - Support for new and existing users- **Webhook Integration** - Receive instant status notifications## Payment Processing Options### 1. Two-Step Process (Create + Commit)**Best for:** Careful review and approval workflows1. **Create Payout** - Generate payout instruction2. **Review Details** - Verify recipient and amount information3. **Commit Payout** - Execute the payment### 2. One-Step Process (Direct)**Best for:** Automated systems and immediate processing- **Create and Execute** - Single API call processes payment immediately- **Streamlined Workflow** - Reduces API calls and complexity- **Instant Processing** - Payment begins processing immediately## Status Management### Payout Status Values| Status | Final? | Description | Next Actions || ----------- | ------ | ---------------------------------------------------------------- | --------------------------- || `created` | No | Payout instruction created, awaiting commit | Call commit endpoint || `committed` | No | Payout committed and queued for processing | Monitor status updates || `pending` | No | Awaiting recipient action (account creation, verification, etc.) | Wait for recipient action || `completed` | Yes | Payment successfully delivered to recipient | None - payment complete || `canceled` | Yes | Payout canceled, funds returned to sender | None - transaction reversed || `failed` | Yes | Payment failed due to processing error | Contact support if needed |### Detailed Status Descriptions#### Created Status- Payout instruction has been successfully created- Funds are not yet committed from your account- You can still modify or cancel the payout- Must call commit endpoint to proceed#### Committed Status- Payout has been committed for processing- Funds are placed in escrow- Processing has begun but not yet completed- Cannot be canceled once committed#### Pending StatusThe payout is waiting for recipient action:- **New User:** Recipient needs to create an Airtm account- **Verification Required:** Recipient exceeds $1,000 threshold and needs ID verification- **US Recipients:** Must complete ID verification and configure payment method- **Account Issues:** Recipient account may have restrictionsA pending payout can still be canceled before it is processed.#### Completed Status- Payment has been successfully processed- Funds have been credited to recipient's account- Final status - no further action needed- Success webhook sent (if configured)#### Canceled Status- Payout was canceled before or during processing- Funds have been returned to your account- Can occur due to: - Manual cancellation - Recipient unable to receive funds - Account restrictions - Compliance issues#### Failed Status- Rare occurrence of processing failure- Contact [enterprise@airtm.com](mailto:enterprise@airtm.com) for assistance- May require manual intervention to resolve## Recipient Management### New RecipientsWhen sending to users who don't have Airtm accounts:1. **Payout Created** - Payment is created with recipient email2. **Email Notification** - Recipient receives invitation to join Airtm3. **Account Creation** - Recipient creates Airtm account4. **Payment Completion** - Funds are automatically credited### Existing RecipientsFor users with existing Airtm accounts:- Payments are typically processed faster- Fewer verification requirements- Direct credit to their account balance### Recipient Verification Requirements#### $1,000+ ThresholdRecipients receiving amounts that bring their total inflow over $1,000 must:- Complete ID verification- Provide government-issued identification- Verify personal information#### US RecipientsAll US-based recipients must:- Complete ID verification regardless of amount- Configure a valid payment method- Meet additional compliance requirements

Airtm Payments / Payouts API is one of 24 APIs that Airtm publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments / Payouts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 5 paths. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://payments.air-pay.io, https://payments.static-stg.tests.airtm.org.

5 operations 5 paths 0 schemas 1 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.enterprise.airtm.com/v2
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Airtm Payments / Payouts API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth).

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 1 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Payments / Payouts 5

Overview The Payouts endpoint enables your organization to send payments to recipients worldwide through the Airtm platform. This powerful endpoint supports both individual and bu…

POST
payouts
Create payout
Payments _ Payouts_payments-payouts/create-payout body → 200
POST
payouts/{payoutId}/commit
Commit payout
Payments _ Payouts_payments-payouts/commit-payout 1 param body → 200404
POST
payouts/one-step
One step payout
Payments _ Payouts_payments-payouts/one-step-payout body → 200
GET
payouts/events/:payoutId
Get payout event
Payments _ Payouts_payments-payouts/get-payout-event → 200
POST
payouts/{payoutId}/cancel
Cancel pending payouts
Payments _ Payouts_payments-payouts/cancel-pending-payments-copy-1 1 param body → 200400500

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

airtm-payments-payouts-api-openapi.yml Raw ↑

Other APIs Airtm publishes across the network.

Airtm Wallet Resource (Connect) API
Airtm Account Status API
Airtm API Keys API
Airtm Bulk Payments API
Airtm Bulk Payouts API
Airtm Deposits API
Airtm Embedded Catalog API
Airtm Embedded Quotes API
Airtm Embedded Receivers API
Airtm Embedded Senders API
Airtm Embedded Transactions API
Airtm External Bank Account API
Where this information came from

This is an independent, third-party profile of Airtm Payments / Payouts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.