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

Tribe Payments Payments API

The Payments API from Tribe Payments — 7 operation(s) for payments.

Tribe Payments Payments API is one of 45 APIs that Tribe Payments publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 7 operations across 7 paths, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

7 operations 7 paths 21 schemas 7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Resource Areas
1

Paths & Operations 7

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

Payments 7
POST
/v2_payment_single
Single payment
body → 200302
POST
/v2_payment_single_status
Get single payment status
body → 200
POST
/v2_payment_bulk
Bulk payment.
body → 200302
POST
/v2_payment_bulk_status
Get bulk payment status
body → 200
POST
/v2_payment_direct_single
Direct payment initiation.
body → 200302
POST
/v2_payment_status
Payment Status Update
body → 200
POST
/v2_payment_confirmation_link_expire
Payment Confirmation Link Expiration
body → 200

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are PaymentSingleRequest (11 properties), AccountTransaction (8 properties), SingleBulkPayment (6 properties), PaymentBulkRequest (6 properties). Each schema is shown below with its type and property counts.

PaymentBulkRequest
object
6 properties 3 required
PaymentSingleRequest
object
11 properties 2 required
PaymentSingleResponse
object
3 properties 3 required
Address
object
5 properties 1 required
PaymentSingleStatusRequest
object
1 property 1 required
CreditorAccount
object
4 properties
DebtorAccount
object
4 properties
CreditorBank
object
3 properties 2 required
SingleBulkPayment
object
6 properties 1 required
PaymentCallbackParameters
object
3 properties 2 required
RemittanceInformationStructured
object
2 properties
InstructedTotals
object
2 properties 2 required
PaymentBulkStatusRequest
object
1 property 1 required
Amount
object
2 properties 2 required
TransactionStatusResponse
object
1 property 1 required
PaymentStatusRequest
object
3 properties 2 required
TransactionAmount
object
4 properties
DebtorAccount_2
object
4 properties
RemittanceInformationStructured_2
object
2 properties
CreditorAccount_2
object
4 properties
AccountTransaction
object
Includes the transaction information if available.
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tribe-payments-payments-api-openapi.yml Raw ↑

Other APIs Tribe Payments publishes across the network.

Issuer Processor - Program Manager API (PM API)
Issuer Processor - Transaction Authorization Interface (TAI API)
Acquiring Processor - Acquirer API (ACAPI)
Acquiring Processor - Merchant API (MAPI)
Acquiring Processor - Terminal API (TAPI)
Acquiring Processor - Tokenization API (TOKAPI)
Bank Connect - Payment Services API
Tribe Payments 3DS authentication required API
Tribe Payments Account API
Tribe Payments Accounts API
Tribe Payments App API
Tribe Payments Authorization API
Where this information came from

This is an independent, third-party profile of Tribe Payments Payments 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.