A positive integer in the smallest currency unit (e.g 100 cents to charge $1.00, or 1 to charge ¥1, a 0-decimal currency) representing how much to charge the card. The minimum amount is $0.50 (or equivalent in charge currency).
3-letter ISO code for currency.
Whether or not to immediately capture the charge. When false, the charge issues an authorization (or pre-authorization), and will need to be captured later. Uncaptured charges expire in 7 days. For more information, see authorizing charges and settling later.
A fee in cents that will be applied to the charge and transferred to the application owner's Stripe account. To use an application fee, the request must be made on behalf of another account, using the Stripe-Account header, an OAuth key, or the Charge.destination parameter. For more information, see the application fees documentation.
An arbitrary string which you can attach to a charge object. It is displayed when in the web interface alongside the charge. Note that if you use Stripe to send automatic email receipts to your customers, your receipt emails will include the description of the charge(s) that they are describing.
An account to make the charge on behalf of. If specified, the charge will be attributed to the destination account for tax reporting, and the funds from the charge will be transferred to the destination account. The ID of the resulting transfer will be returned in the transfer field of the response. See the documentation for details.
A set of key/value pairs that you can attach to a charge object. It can be useful for storing additional information about the customer in a structured format. It's often a good idea to store an email address in metadata for tracking later.
The email address to send this charge's receipt to. The receipt will not be sent until the charge is paid. If this charge is for a customer, the email address specified here will override the customer's email address. Receipts will not be sent for test mode charges. If receiptEmail is specified for a charge in live mode, a receipt will be sent regardless of your email settings.
Shipping information for the charge. Helps prevent fraud on charges for physical goods. For more information, see the Charge object documentation.
The ID of an existing customer that will be charged in this request.
A payment source to be charged, such as a credit card. If you also pass a customer ID, the source must be the ID of a source belonging to the customer. Otherwise, if you do not pass a customer ID, the source you provide must either be a token, like the ones returned by Stripe.js, or a dictionary containing a user's credit card details, with the options described below. Although not all information is required, the extra info helps prevent fraud.
An arbitrary string to be displayed on your customer's credit
card statement. This may be up to 22 characters. 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 statementDescriptor
of RunClub 5K race ticket. The statement description may not include <>"'
characters,
and will appear on your customer's statement in capital letters.
Non-ASCII characters are automatically stripped. While most banks display
this information consistently, some may display it incorrectly or not at all.
StatementDescriptorInvalidCharacter
- If statementDescriptor has an invalid character
StatementDescriptorTooLong
- If statementDescriptor is longer than 22 characters
A positive integer in the smallest currency unit (e.g 100 cents to charge $1.00, or 1 to charge ¥1, a 0-decimal currency) representing how much to charge the card.
A positive integer in the smallest currency unit (e.g 100 cents to charge $1.00, or 1 to charge ¥1, a 0-decimal currency) representing how much to charge the card. The minimum amount is $0.50 (or equivalent in charge currency).
A fee in cents that will be applied to the charge and transferred to the application owner's Stripe account.
A fee in cents that will be applied to the charge and transferred to the application owner's Stripe account. To use an application fee, the request must be made on behalf of another account, using the Stripe-Account header, an OAuth key, or the Charge.destination parameter. For more information, see the application fees documentation.
Whether or not to immediately capture the charge.
Whether or not to immediately capture the charge. When false, the charge issues an authorization (or pre-authorization), and will need to be captured later. Uncaptured charges expire in 7 days. For more information, see authorizing charges and settling later.
3-letter ISO code for currency.
The ID of an existing customer that will be charged in this request.
An arbitrary string which you can attach to a charge object.
An arbitrary string which you can attach to a charge object. It is displayed when in the web interface alongside the charge. Note that if you use Stripe to send automatic email receipts to your customers, your receipt emails will include the description of the charge(s) that they are describing.
An account to make the charge on behalf of.
An account to make the charge on behalf of. If specified, the charge will be attributed to the destination account for tax reporting, and the funds from the charge will be transferred to the destination account. The ID of the resulting transfer will be returned in the transfer field of the response. See the documentation for details.
A set of key/value pairs that you can attach to a charge object.
A set of key/value pairs that you can attach to a charge object. It can be useful for storing additional information about the customer in a structured format. It's often a good idea to store an email address in metadata for tracking later.
The email address to send this charge's receipt to.
The email address to send this charge's receipt to. The receipt will not be sent until the charge is paid. If this charge is for a customer, the email address specified here will override the customer's email address. Receipts will not be sent for test mode charges. If receiptEmail is specified for a charge in live mode, a receipt will be sent regardless of your email settings.
Shipping information for the charge.
Shipping information for the charge. Helps prevent fraud on charges for physical goods. For more information, see the Charge object documentation.
A payment source to be charged, such as a credit card.
A payment source to be charged, such as a credit card. If you also pass a customer ID, the source must be the ID of a source belonging to the customer. Otherwise, if you do not pass a customer ID, the source you provide must either be a token, like the ones returned by Stripe.js, or a dictionary containing a user's credit card details, with the options described below. Although not all information is required, the extra info helps prevent fraud.
An arbitrary string to be displayed on your customer's credit card statement.
An arbitrary string to be displayed on your customer's credit
card statement. This may be up to 22 characters. 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 statementDescriptor
of RunClub 5K race ticket. The statement description may not include <>"'
characters,
and will appear on your customer's statement in capital letters.
Non-ASCII characters are automatically stripped. While most banks display
this information consistently, some may display it incorrectly or not at all.
A positive integer in the smallest currency unit (e.g 100 cents to charge $1.00, or 1 to charge ¥1, a 0-decimal currency) representing how much to charge the card. The minimum amount is $0.50 (or equivalent in charge currency).
3-letter ISO code for currency.
Whether or not to immediately capture the charge. When false, the charge issues an authorization (or pre-authorization), and will need to be captured later. Uncaptured charges expire in 7 days. For more information, see authorizing charges and settling later.
A fee in cents that will be applied to the charge and transferred to the application owner's Stripe account. To use an application fee, the request must be made on behalf of another account, using the Stripe-Account header, an OAuth key, or the Charge.destination parameter. For more information, see the application fees documentation.
An arbitrary string which you can attach to a charge object. It is displayed when in the web interface alongside the charge. Note that if you use Stripe to send automatic email receipts to your customers, your receipt emails will include the description of the charge(s) that they are describing.
An account to make the charge on behalf of. If specified, the charge will be attributed to the destination account for tax reporting, and the funds from the charge will be transferred to the destination account. The ID of the resulting transfer will be returned in the transfer field of the response. See the documentation for details.
A set of key/value pairs that you can attach to a charge object. It can be useful for storing additional information about the customer in a structured format. It's often a good idea to store an email address in metadata for tracking later.
The email address to send this charge's receipt to. The receipt will not be sent until the charge is paid. If this charge is for a customer, the email address specified here will override the customer's email address. Receipts will not be sent for test mode charges. If receiptEmail is specified for a charge in live mode, a receipt will be sent regardless of your email settings.
Shipping information for the charge. Helps prevent fraud on charges for physical goods. For more information, see the Charge object documentation.
The ID of an existing customer that will be charged in this request.
A payment source to be charged, such as a credit card. If you also pass a customer ID, the source must be the ID of a source belonging to the customer. Otherwise, if you do not pass a customer ID, the source you provide must either be a token, like the ones returned by Stripe.js, or a dictionary containing a user's credit card details, with the options described below. Although not all information is required, the extra info helps prevent fraud.
An arbitrary string to be displayed on your customer's credit card statement. This may be up to 22 characters. 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 statementDescriptor of RunClub 5K race ticket. The statement description may not include
<>"'
characters, and will appear on your customer's statement in capital letters. Non-ASCII characters are automatically stripped. While most banks display this information consistently, some may display it incorrectly or not at all.StatementDescriptorInvalidCharacter
- If statementDescriptor has an invalid characterStatementDescriptorTooLong
- If statementDescriptor is longer than 22 charactershttps://stripe.com/docs/api#create_charge