POST /v1/sources

Default value: "application/x-www-form-urlencoded"

Specifies which fields in the response should be expanded.

Information about the items and shipping associated with the source. Required for transactional credit (for example Klarna) sources before you can charge it.

Possible values:

• "sku"
• "shipping"
• "discount"
• "tax"

Three-letter ISO code for the currency associated with the source. This is the currency for which the source will be chargeable once ready.

Parameters required for the redirect flow. Required if the source is authenticated by a redirect (flow is redirect).

Optional parameters for the receiver flow. Can be set only if the source is a receiver (flow is receiver).

Possible values:

• "manual"
• "email"
• "none"

Possible values:

• "single_use"
• "reusable"

The Customer to whom the original source is attached to. Must be set when the original source is not a Source (e.g., Card).

The authentication flow of the source to create. flow is one of redirect, receiver, code_verification, none. It is generally inferred unless a type supports multiple flows.

Possible values:

• "receiver"
• "code_verification"
• "redirect"
• "none"

Amount associated with the source. This is the amount for which the source will be chargeable once ready. Required for single_use sources. Not supported for receiver type sources, where charge amount may not be specified until funds land.

Information about a mandate possibility attached to a source object (generally for bank debits) as well as its acceptance status.

Possible values:

• "variable"
• "scheduled"
• "one_time"

Possible values:

• "manual"
• "email"
• "stripe_email"
• "deprecated_none"
• "none"

Possible values:

• "offline"
• "online"

Possible values:

• "refused"
• "pending"
• "revoked"
• "accepted"

An optional token used to create the source. When passed, token properties will override source parameters.

The source to share.

The type of the source to create. Required unless customer and original_source are specified (see the Cloning card Sources guide)

Information about the owner of the payment instrument that may be used or required by particular source types.

An arbitrary string to be displayed on your customer's statement. As an example, if your website is RunClub and the item you're charging for is a race ticket, you may want to specify a statement_descriptor of RunClub 5K race ticket. While many payment types will display this information, some may not display it at all.