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

BackBase Validate API

Validation of a payment.

BackBase Validate API is one of 8 APIs that BackBase publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 12 JSON Schema definitions.

Tagged areas include Validate. The published artifact set on APIs.io includes an OpenAPI specification and 12 JSON Schemas.

This API exposes 1 operation across 1 path, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against 3 base URLs: http://localhost:4010, http://localhost:8080, https://localhost:8081.

1 operations 1 paths 21 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.backbase.com
Resource Areas
1

Paths & Operations 1

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

Validate 1

Validation of a payment.

POST
/client-api/v2/payment-orders/validate
Validate a payment order
postValidate body → 200500400

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are PaymentOrdersValidatePostResponse (17 properties), IdentifiedTransaction (14 properties), InitiateTransaction (14 properties), PaymentOrdersValidatePost (10 properties). Each schema is shown below with its type and property counts.

Schedule
object
Schedule for recurring transfer. Mandatory if paymentMode is RECURRING
8 properties 4 required
AccountIdentification
object
2 properties 1 required
SelectedContactDto
object
Holds the contact and account id when an account from a contact was selected while creating a payment. This information is not persisted in DBS but can be used…
2 properties
IdentifiedTransaction
object
The object defining the identified transaction, which means the counterparty will have a arrangementId where applicable.
14 properties 3 required
InitiateTransaction
object
The object defining the transaction to be initiated.
14 properties 3 required
PaymentOrdersValidatePost
object
10 properties 3 required
ExchangeRateInformation
object
The detailed information on the exchange rate that has been used in the payment transaction.
4 properties
InitiateCounterpartyAccount
object
The counterparty Account is the original account identification plus the type of account if applicable. It also holds the details of the selected contact, if a…
2 properties
PostalAddress
object
Postal address object with fields
7 properties
internal-server-error
object
Represents HTTP 500 Internal Server Error
1 property
PaymentOrdersValidatePostResponse
object
17 properties 3 required
OriginatorAccount
object
The product identification of the originator
4 properties 2 required
error-item
object
3 properties
Identification
object
2 properties 2 required
CounterpartyAccount
object
The counterparty Account is the original account identification plus the arrangement if applicable.
5 properties 1 required
currency
object
3 properties 2 required
Bank
object
This object is used to identify the counterparty or correspondent bank.
4 properties
bad-request-error
object
2 properties 1 required
RemittanceInformation
object
This is the object representation of the remittance info and can contain different types of remittance info. It is only used in responses, not for input reques…
2 properties 2 required
Currency
InvolvedParty
object
This object is a common denominator for the debtor or creditor party.
4 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

backbase-validate-api-openapi.yml Raw ↑

Other APIs BackBase publishes across the network.

BackBase Approve API
BackBase Bbt API
BackBase Patch API
BackBase Payment Orders API
BackBase Test API
BackBase Utility API
BackBase Wallet API
Where this information came from

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