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 Direct payments without Bank API

Endpoints for executing direct payments (without acquiring previous consent).

Tribe Payments Direct payments without Bank 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 Direct payments without Bank. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

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

Requests are made against a single base URL, %tpp_api_url%/tpp/v2.

3 operations 3 paths 21 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Server
%tpp_api_url%/tpp/v2
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Tribe Payments Direct payments without Bank API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (tokenAuth). An API key is passed in the header as X-Client-ID (clientId). By default, every request must be authenticated.

Paths & Operations 3

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

Direct payments without Bank 3

Endpoints for executing direct payments (without acquiring previous consent).

POST
/direct/payments
Initiate a single new payment, with PSU selecting ASPSP during SCA.
7 params body → 201400401403405406415429
GET
/direct/payments/{paymentId}
Retrieve content of an initiated payment.
6 params → 200400401403404405406429
GET
/direct/payments/{paymentId}/status
Retrieve current status of an initiated payment.
6 params → 200400401403404405406429

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are SinglePayment (10 properties), CreditorAddress (5 properties), ForbiddenError (5 properties), NotAllowedError (5 properties). Each schema is shown below with its type and property counts.

PaymentResponse
object
A JSON body.
3 properties 2 required
BankReference
object
The information about the payment receiver's institution. Mandatory to use with the [SWIFT](appendix--enum--payment-schemes) payment scheme.
3 properties
AccountReference
object
The identifier of the addressed account.
4 properties
UnsupportedMediaTypeError
object
An unsupported Content-Type header.
5 properties 3 required
TransactionStatus
object
Contains status of the payment.
1 property
NotFoundError
object
Not found.
5 properties 3 required
NotAcceptableError
object
An unsupported Accept header.
5 properties 3 required
EmptyAdditionalErrors
array
NotAllowedError
object
A forbidden HTTP method.
5 properties 3 required
ForbiddenError
object
The forbidden error object example.
5 properties 3 required
InternalServerError
object
The forbidden error object example.
5 properties 3 required
UnauthorizedError
object
The unauthorized error object example.
5 properties 3 required
Error
object
The generic error object example.
5 properties 3 required
SinglePayment
object
A JSON structure initiating a single payment.
10 properties 3 required
AccessExceededError
object
The forbidden error object example.
5 properties 3 required
ScaRedirect
object
The link to which to redirect the PSU browser for a SCA confirmation of the payment.
1 property
StructuredAmount
object
An amount with a currency.
2 properties 2 required
RemittanceInformationStructured
object
The reference as contained in the structured remittance reference structure.
2 properties 1 required
AdditionalError
object
The error object providing additional error information.
3 properties 1 required
CreditorAddress
object
An address of the account holder.
5 properties 1 required
PaymentLinks
object
Contains redirect information for a payment confirmation.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tribe-payments-direct-payments-without-bank-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 Direct payments without Bank 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.