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

Truist Credit Transfers

Process real-time credit transfer payments to and from eligible accounts. Credit Transfers API Truist publishes an OpenAPI 3.1.0 contract (v2.6.0) for this product on the Truist Developer Center.

Truist Credit Transfers is one of 15 APIs that BB&T Corp (Truist) publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Banking, Commercial Banking, Open Banking, and Real-time payments. The published artifact set on APIs.io includes API documentation and an OpenAPI specification.

This API exposes 7 operations across 4 paths, organized into 4 resource areas, and defines 31 schemas. It is described by OpenAPI 3.1.0, at version 2.6.0.

Requests are made against 3 base URLs: https://api-sandbox.truist.com/commercial, https://apicert.truist.com/commercial, https://api.truist.com/commercial.

7 operations 4 paths 31 schemas 3 GET3 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.6.0
Base URL
https://api.truist.com/commercial
Authentication
OAuth 2.0
Resource Areas
4

Authentication & Security 1

Truist Credit Transfers declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth) using the authorizationCode flow, exposing 3 scopes.

  • OAuth — The production authorization URL will be provided after the onboarding process is completed.

Paths & Operations 7

Across 4 paths, the API surfaces 7 operations — 3 GET, 3 POST, 1 PUT. They span 4 resource areas: Credit Transfers, Credit Transfers Account List, Credit Transfers Approval/Reject, Credit Transfers Acknowledge. Each is listed below with its method, path, parameters, and response codes.

Credit Transfers 3

Credit Transfers for a Real Time Payment

POST
/v2/payments/rtp/credit-transfers
Post credit transfers
createRtpCreditTransfer 1 param body → 200400401403404405429409
GET
/v2/payments/rtp/credit-transfers
Get credit transfers
getRealTimePaymentTransactions 13 params → 200400401404405429500503
PUT
/v2/payments/rtp/credit-transfers
Credit transfers cancel
updatePaymentStatus 1 param body → 200400401403404405500503
Credit Transfers Account List 1

Eligible accounts for Real Time Payment Credit Transfer

GET
/v2/payments/rtp/credit-transfers/accounts
Get accounts
getEligibleCreditTransfer 2 params → 200401403404405429500503
Credit Transfers Approval/Reject 2

Approvals for Real Time Payment Credit Transfer

POST
/v2/payments/rtp/credit-transfers/approvals
Post credit transfers
createRtpCreditTransferApprove 1 param body → 200400401403404405429500
GET
/v2/payments/rtp/credit-transfers/approvals
Get credit transfer approval list
getRealTimePaymentApprovals 5 params → 200400401403404405429500
Credit Transfers Acknowledge 1

Credit Transfer Acknowledge for an inbound credit transfer

POST
/v2/payments/rtp/credit-transfers/{paymentId}/acknowledgements
Post credit transfers acknowledge
createRtpPaymentAcknowledgment 2 params body → 200400401403404405429500

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are Transaction (23 properties), RtpCreditor (11 properties), Account (8 properties), RtpPaymentDetail (8 properties). Each schema is shown below with its type and property counts.

CorrelationId
string
The Correlation ID is unique ID made by removing hyphens from a standard UUID to make it 32 characters long.
AccountList
object
Accounts returned by API upon successful search
1 property
Account
object
List of commercial accounts for a user
8 properties
AccountType
string
Account type identified by the bank
Error
object
An error entity which can be used at the API level for error responses or at the account level to indicate a problem specific to a particular account
2 properties
AcknowledgePaymentRequest
object
Payment acknowledgement request for credit transfer
1 property
AcknowledgePaymentResponse
object
Payment acknowledgement response for credit transfer
1 property
RtpPaymentRequest
object
Real-Time payment, pacs.008, Intiate Transfer from one account number to several recipients
PaymentType
string
TCH Payment type
PaymentSubType
string
The subtype of a submitted RTP: - RTP Credit Type - Request for Return of Funds - Inbound Request Credit
PaymentIds
object
Correlation and payment IDs for the payment
2 properties
RtpPaymentDetail
object
Payment and recipient information
8 properties 4 required
RtpResponse
object
Status of the RTP Transfer
1 property
UpdatePaymentRequest
object
Update payment status
2 properties 2 required
UpdateStatus
string
Update payment status
CancelPaymentRequest
object
Update payment status
2 properties 2 required
CancelStatus
string
Update payment status
GetApprovalsPaymentResponse
object
Real time payment transaction list
1 property
UpdatePaymentResponse
object
response for successful status update
2 properties 1 required
Address
object
5 properties 4 required
ContactDetails
object
5 properties
Iso3166CountryCode
string
ISO 3166-1 alpha-2 codes as of April 5, 2023, from officially assigned Country Codes on [ISO Online Browsing Platform](https://www.iso.org/obp/ui/)
PaymentAction
string
The payment action of a submitted RTP: - sent - received
RtpStatus
string
The status of a submitted RTP: - needsApproval - rejected - approved - completed - canceled - scheduled - processing - rejectedByApprover - failed - expired -…
RtpTransactionStatus
string
The status of a submitted RTP: - needsApproval - rejected - approved - completed - canceled - scheduled - processing - rejectedByApprover - failed - expired
RtpCreditor
object
Common details for RtpCreditor
11 properties 2 required
Transactions
object
Real time payment transaction list
2 properties
PageMetadata
object
Offset IDs for paginated result sets
2 properties
Transaction
object
payment transaction inquiry response payload
23 properties 5 required
PaymentDate
string
Date to dispatch the payment. ISO 8601 date as "yyyy-mm-dd". Only applicable for future dated(OTFD) and One time payments.
MultipleRtpPaymentRequest
object
Object for holding multiple payment transfers.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bbandt-corp-commercial-credit-transfers-oas-v2-openapi.yml Raw ↑

Other APIs BB&T Corp (Truist) publishes across the network.

Truist Commercial Accounts
Truist Commercial Account Balance
Truist Commercial Account Transactions
Truist Personal and Small Business Accounts
Truist Branch/ATM Locator
Truist Personal and Small Business Transactions
Truist Personal and Small Business Client Contact
Truist Retail Oauth Authentication
Truist User Consent
Truist Retail Dynamic Client Registration
Truist Personal and Small Business Account Payment Networks
Truist Account Address
Where this information came from

This is an independent, third-party profile of Truist Credit Transfers, 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.