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

Stripe Sources API

Source objects allow you to accept a variety of payment methods. They represent a customer's payment instrument, and can be used with the Stripe API just like a Card object once chargeable, they can be charged, or can be attached to customers.

Stripe Sources API is one of 159 APIs that Stripe publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Sources and Transaction. The published artifact set on APIs.io includes API documentation and an OpenAPI specification.

This API exposes 13 operations across 9 paths, and defines 29 schemas. It is described by OpenAPI 3.2.0, at version 2023-10-16.

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

13 operations 9 paths 29 schemas 1 DELETE6 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2023-10-16
Server
https://api.stripe.com/
Authentication
HTTP Basic, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 2

Stripe Sources API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It accepts HTTP bearer tokens (auth-scheme) (bearerAuth). By default, every request must be authenticated.

  • basicAuth — Basic HTTP authentication. Allowed headers-- Authorization: Basic | Authorization: Basic
  • bearerAuth — Bearer HTTP authentication. Allowed headers-- Authorization: Bearer

Paths & Operations 13

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

Sources 13
GET
/v1/customers/{customer}/sources
Stripe Get Customers Customer Sources
getCustomersCustomerSources 6 params body → 200default
POST
/v1/customers/{customer}/sources
Stripe Post Customers Customer Sources
postCustomersCustomerSources 1 param body → 200default
DELETE
/v1/customers/{customer}/sources/{id}
Stripe Delete Customers Customer Sources Id
deleteCustomersCustomerSourcesId 2 params body → 200default
GET
/v1/customers/{customer}/sources/{id}
Stripe Get Customers Customer Sources Id
getCustomersCustomerSourcesId 3 params body → 200default
POST
/v1/customers/{customer}/sources/{id}
Stripe Post Customers Customer Sources Id
postCustomersCustomerSourcesId 2 params body → 200default
POST
/v1/customers/{customer}/sources/{id}/verify
Stripe Post Customers Customer Sources Id Verify
postCustomersCustomerSourcesIdVerify 2 params body → 200default
POST
/v1/sources
Creates a new source object.
PostSources body → 200default
GET
/v1/sources/{source}
Retrieves an existing source object. Supply the unique source ID from a source creation request and Stripe will return the corresponding up-to-date source object information.
GetSourcesSource 3 params body → 200default
POST
/v1/sources/{source}
Updates the specified source by setting the values of the parameters passed. Any parameters not provided will be left unchanged. This request accepts the metadata and owner as arguments. It is also p…
PostSourcesSource 1 param body → 200default
GET
/v1/sources/{source}/mandate_notifications/{mandate_notification}
Retrieves a new Source MandateNotification.
GetSourcesSourceMandateNotificationsMandateNotification 3 params body → 200default
GET
/v1/sources/{source}/source_transactions
List source transactions for a given source.
GetSourcesSourceSourceTransactions 5 params body → 200default
GET
/v1/sources/{source}/source_transactions/{source_transaction}
Retrieve an existing source transaction object. Supply the unique source ID from a source creation request and the source transaction ID and Stripe will return the corresponding up-to-date source obj…
GetSourcesSourceSourceTransactionsSourceTransaction 3 params body → 200default
POST
/v1/sources/{source}/verify
Verify a given source.
PostSourcesSourceVerify 1 param body → 200default

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are payment_method (43 properties), subscription (43 properties), source (37 properties), card (28 properties). Each schema is shown below with its type and property counts.

customer
object
This object represents a customer of your business. Use it to create recurring charges and track payments that belong to the same customer. Related guide: [Sav…
28 properties 4 required
PostCustomersCustomerSourcesIdVerifyRequest
object
2 properties
DeleteCustomersCustomerSourcesIdRequest
object
1 property
payment_method
object
PaymentMethod objects represent your customer's payment instruments. You can use them with [PaymentIntents](https://stripe.com/docs/payments/payment-intents) t…
43 properties 6 required
subscription
object
Subscriptions allow you to charge a customer on a recurring basis. Related guide: [Creating subscriptions](https://stripe.com/docs/billing/subscriptions/creati…
43 properties 16 required
GetSourcesSourceSourceTransactionsRequest
object
deleted_customer
object
3 properties 3 required
GetCustomersCustomerSourcesIdRequest
object
ApmsSourcesSourceList
object
4 properties 4 required
card
object
You can store multiple cards on a customer in order to charge the customer later. You can also store multiple debit cards on a recipient in order to transfer t…
28 properties 7 required
tax_id
object
You can add one or multiple tax IDs to a [customer](https://stripe.com/docs/api/customers) or account. Customer and account tax IDs get displayed on related in…
9 properties 6 required
source
object
Source objects allow you to accept a variety of payment methods. They represent a customer's payment instrument, and can be used with the Stripe API just like…
37 properties 8 required
GetSourcesSourceRequest
object
PostSourcesSourceRequest
object
6 properties
source_transaction
object
Some payment methods have no required amount that a customer must send. Customers can be instructed to send any amount, and it can be made up of multiple trans…
14 properties 9 required
error
object
An error response from the Stripe API
1 property 1 required
source_mandate_notification
object
Source mandate notifications should be created when a notification related to a source mandate must be sent to the payer. They will trigger a webhook or delive…
12 properties 8 required
bank_account
object
These bank accounts are payment methods on Customer objects. On the other hand [External Accounts](https://stripe.com/docs/apiexternalaccounts) are transfer de…
19 properties 6 required
PostSourcesSourceVerifyRequest
object
2 properties 1 required
PostCustomersCustomerSourcesIdRequest
object
14 properties
ApmsSourcesSourceTransactionList
object
4 properties 4 required
PostSourcesRequest
object
16 properties
GetSourcesSourceMandateNotificationsMandateNotificationRequest
object
PostCustomersCustomerSourcesRequest
object
6 properties
payment_source
GetCustomersCustomerSourcesRequest
object
GetSourcesSourceSourceTransactionsSourceTransactionRequest
object
discount
object
A discount represents the actual application of a [coupon](https://stripe.com/docs/apicoupons) or [promotion code](https://stripe.com/docs/apipromotioncodes).…
11 properties 4 required
cash_balance
object
A customer's Cash balance represents real funds. Customers can add funds to their cash balance by sending a bank transfer. These funds can be used for payment…
5 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

stripe-sources-api-openapi.yml Raw ↑

Other APIs Stripe publishes across the network.

Stripe Accounts API
Stripe Balance API
Stripe Billing API
Stripe Charges API
Stripe Checkout API
Stripe Climate API
Stripe Country API
Stripe Coupons API
Stripe Credit Notes API
Stripe Customers API
Stripe Disputes API
Stripe Ephemeral Keys API
Where this information came from

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