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

US Bancorp Request for Payment API

The Request for Payment API from US Bancorp — 2 operation(s) for request for payment.

US Bancorp Request for Payment API is one of 15 APIs that US Bancorp publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Request for Payment. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, and 2 JSON Schemas.

This API exposes 2 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against a single base URL, https://api.usbank.com/v1.

2 operations 2 paths 3 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://api.usbank.com
Authentication
OAuth 2.0
Terms of Service
Resource Areas
1

Authentication & Security 1

US Bancorp Request for Payment API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2MFA) using the authorizationCode flow, exposing 2 scopes. By default, every request must be authenticated.

  • OAuth2MFA — OAuth 2.0 with MFA using SinglePoint credentials

Paths & Operations 2

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

Request for Payment 2
POST
/rtp/requests-for-payment
Initiate RTP Request for Payment
initiateRTPRequestForPayment 2 params body → 201400
GET
/rtp/requests-for-payment/{requestId}
Get RTP Request for Payment Status
getRTPRequestForPaymentStatus 3 params → 200404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are RequestForPaymentRequest (8 properties), RequestForPaymentResponse (4 properties), Error (3 properties). Each schema is shown below with its type and property counts.

RequestForPaymentResponse
object
4 properties 4 required
RequestForPaymentRequest
object
Request to initiate an RTP Request for Payment
8 properties 3 required
Error
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

us-bancorp-request-for-payment-api-openapi.yml Raw ↑

Other APIs US Bancorp publishes across the network.

US Bank Wire Transfers API
US Bank Data Toolbox API
US Bank Voyager Fleet API
US Bank Freight Payment API
US Bank Instant Payments API
US Bank Holidays API
US Bancorp Accounts API
US Bancorp Balances API
US Bancorp Credit Transfers API
US Bancorp Exception History API
US Bancorp Exceptions API
US Bancorp Push to Card Payments API
Where this information came from

This is an independent, third-party profile of US Bancorp Request for Payment 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.