Create or replace a secret in the secret store.
" }, { "info": { "name": "Stripe Post Apps Secrets Delete", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/apps/secrets/delete", "body": { "type": "form-urlencoded", "data": [ { "name": "expand", "value": "" }, { "name": "name", "value": "" }, { "name": "scope", "value": "" } ] } }, "docs": "Deletes a secret from the secret store by name and scope.
" }, { "info": { "name": "Stripe Post Billing Portal Configurations", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/billing_portal/configurations", "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Creates a configuration that describes the functionality and behavior of a PortalSession
" }, { "info": { "name": "Stripe Post Billing Portal Configurations Configuration", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/billing_portal/configurations/:configuration", "params": [ { "name": "configuration", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Updates a configuration that describes the functionality of the customer portal.
" }, { "info": { "name": "Stripe Post Billing Portal Sessions", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/billing_portal/sessions", "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Creates a session of the customer portal.
" }, { "info": { "name": "Stripe Post Checkout Sessions", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/checkout/sessions", "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Creates a Session object.
" }, { "info": { "name": "Stripe Post Checkout Sessions Session Expire", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/checkout/sessions/:session/expire", "params": [ { "name": "session", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "A Session can be expired when it is in one of these statuses: open
After it expires, a customer can’t complete a Session and customers loading the Session see a message saying the Session is expired.
" }, { "info": { "name": "Stripe Post Coupons", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/coupons", "body": { "type": "form-urlencoded", "data": [] } }, "docs": "You can create coupons easily via the coupon management page of the Stripe dashboard. Coupon creation is also accessible via the API if you need to create coupons on the fly.
\n\nA coupon has either a percent_off or an amount_off and currency. If you set an amount_off, that amount will be subtracted from any invoice’s subtotal. For example, an invoice with a subtotal of
Issue a credit note to adjust the amount of a finalized invoice. For a status=open invoice, a credit note reduces\nits amount_due. For a status=paid invoice, a credit note does not affect its amount_due. Instead, it can result\nin any combination of the following:
refund_amount) or link an existing refund (using refund).Updates an existing credit note.
" }, { "info": { "name": "Stripe Post Credit Notes Id Void", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/credit_notes/:id/void", "params": [ { "name": "id", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Marks a credit note as void. Learn more about voiding credit notes.
" }, { "info": { "name": "Stripe Post Customers", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/customers", "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Creates a new customer object.
" }, { "info": { "name": "Stripe Post Customers Customer", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/customers/:customer", "params": [ { "name": "customer", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Updates the specified customer by setting the values of the parameters passed. Any parameters not provided will be left unchanged. For example, if you pass the source parameter, that becomes the customer’s active source (e.g., a card) to be used for all charges in the future. When you update a customer to a new valid card source by passing the source parameter: for each of the customer’s current subscriptions, if the subscription bills automatically and is in" }, { "info": { "name": "Stripe Post Customers Customer Balance Transactions", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/customers/:customer/balance_transactions", "params": [ { "name": "customer", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "
Creates an immutable transaction that updates the customer’s credit balance.
" }, { "info": { "name": "Stripe Post Customers Customer Balance Transactions Transaction", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/customers/:customer/balance_transactions/:transaction", "params": [ { "name": "customer", "value": "", "type": "path" }, { "name": "transaction", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Most credit balance transaction fields are immutable, but you may update its description and metadata.
When you create a new credit card, you must specify a customer or recipient on which to create it.
\n\nIf the card’s owner has no default card, then the new card will become the default.\nHowever, if the owner already has a default, then it will not change.\nTo change the default, you should update the customer to have a new default_source.
Update a specified source for a given customer.
" }, { "info": { "name": "Stripe Post Customers Customer Bank Accounts Id Verify", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/customers/:customer/bank_accounts/:id/verify", "params": [ { "name": "customer", "value": "", "type": "path" }, { "name": "id", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Verify a specified bank account for a given customer.
" }, { "info": { "name": "Stripe Post Customers Customer Cards", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/customers/:customer/cards", "params": [ { "name": "customer", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "When you create a new credit card, you must specify a customer or recipient on which to create it.
\n\nIf the card’s owner has no default card, then the new card will become the default.\nHowever, if the owner already has a default, then it will not change.\nTo change the default, you should update the customer to have a new default_source.
Update a specified source for a given customer.
" }, { "info": { "name": "Stripe Post Customers Customer Cash Balance", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/customers/:customer/cash_balance", "params": [ { "name": "customer", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Changes the settings on a customer’s cash balance.
" }, { "info": { "name": "Stripe Post Customers Customer Funding Instructions", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/customers/:customer/funding_instructions", "params": [ { "name": "customer", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Retrieve funding instructions for a customer cash balance. If funding instructions do not yet exist for the customer, new\nfunding instructions will be created. If funding instructions have already been created for a given customer, the same\nfunding instructions will be retrieved. In other words, we will return the same funding instructions each time.
" }, { "info": { "name": "Stripe Post Customers Customer Sources", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/customers/:customer/sources", "params": [ { "name": "customer", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "When you create a new credit card, you must specify a customer or recipient on which to create it.
\n\nIf the card’s owner has no default card, then the new card will become the default.\nHowever, if the owner already has a default, then it will not change.\nTo change the default, you should update the customer to have a new default_source.
Update a specified source for a given customer.
" }, { "info": { "name": "Stripe Post Customers Customer Sources Id Verify", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/customers/:customer/sources/:id/verify", "params": [ { "name": "customer", "value": "", "type": "path" }, { "name": "id", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Verify a specified bank account for a given customer.
" }, { "info": { "name": "Stripe Post Customers Customer Subscriptions", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/customers/:customer/subscriptions", "params": [ { "name": "customer", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Creates a new subscription on an existing customer.
" }, { "info": { "name": "Stripe Post Customers Customer Subscriptions Subscription Exposed Id", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/customers/:customer/subscriptions/:subscription_exposed_id", "params": [ { "name": "customer", "value": "", "type": "path" }, { "name": "subscription_exposed_id", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Updates an existing subscription on a customer to match the specified parameters. When changing plans or quantities, we will optionally prorate the price we charge next month to make up for any price changes. To preview how the proration will be calculated, use the upcoming invoice endpoint.
" }, { "info": { "name": "Stripe Post Customers Customer Tax Ids", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/customers/:customer/tax_ids", "params": [ { "name": "customer", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Creates a new tax_id object for a customer.
When you get a dispute, contacting your customer is always the best first step. If that doesn’t work, you can submit evidence to help us resolve the dispute in your favor. You can do this in your dashboard, but if you prefer, you can use the API to submit evidence programmatically.
\n\nDepending on your dispute type, different evidence fields will give you a better chance of winning your dispute. To figure out which evidence fields to pr" }, { "info": { "name": "Stripe Post Disputes Dispute Close", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/disputes/:dispute/close", "params": [ { "name": "dispute", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "
Closing the dispute for a charge indicates that you do not have any evidence to submit and are essentially dismissing the dispute, acknowledging it as lost.
\n\nThe status of the dispute will change from needs_response to lost. Closing a dispute is irreversible.
Creates a short-lived API key for a given resource.
" }, { "info": { "name": "Stripe Post Files", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/files", "body": { "type": "multipart-form", "data": [] } }, "docs": "To upload a file to Stripe, you need to send a request of type multipart/form-data. Include the file you want to upload in the request, and the parameters for creating a file.
All of Stripe’s officially supported Client libraries support sending multipart/form-data.
Disables your access to a Financial Connections Account. You will no longer be able to access data associated with the account (e.g. balances, transactions).
Refreshes the data associated with a Financial Connections Account.
Subscribes to periodic refreshes of data associated with a Financial Connections Account.
Unsubscribes from periodic refreshes of data associated with a Financial Connections Account.
To launch the Financial Connections authorization flow, create a Session. The session’s client_secret can be used to launch the flow using Stripe.js.
Creates a VerificationSession object.
\n\nAfter the VerificationSession is created, display a verification modal using the session client_secret or send your users to the session’s url.
If your API key is in test mode, verification checks won’t actually process, though everything else will occur as if in live mode.
\n\nRelated guide: Verify your users’ identity documents
" }, { "info": { "name": "Stripe Post Identity Verification Sessions Session", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/identity/verification_sessions/:session", "params": [ { "name": "session", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Updates a VerificationSession object.
\n\nWhen the session status is requires_input, you can use this method to update the\nverification check and options.
A VerificationSession object can be canceled when it is in requires_input status.
Once canceled, future submission attempts are disabled. This cannot be undone. Learn more.
" }, { "info": { "name": "Stripe Post Identity Verification Sessions Session Redact", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/identity/verification_sessions/:session/redact", "params": [ { "name": "session", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Redact a VerificationSession to remove all collected information from Stripe. This will redact\nthe VerificationSession and all objects related to it, including VerificationReports, Events,\nrequest logs, etc.
\n\nA VerificationSession object can be redacted when it is in requires_input or verified\nstatus. Redacting a VerificationSession in requires_action\nstate will automatically cancel it.
The re" }, { "info": { "name": "Stripe Post Invoice Items", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/Invoice Items", "body": { "type": "form-urlencoded", "data": [] } }, "docs": "
Creates an item to be added to a draft invoice (up to 250 items per invoice). If no invoice is specified, the item will be on the next invoice created for the customer specified.
" }, { "info": { "name": "Stripe Post Invoice Items", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/Invoice Items/:invoiceitem", "params": [ { "name": "invoiceitem", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Updates the amount or description of an invoice item on an upcoming invoice. Updating an invoice item is only possible before the invoice it’s attached to is closed.
" }, { "info": { "name": "Stripe Post Invoices", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/invoices", "body": { "type": "form-urlencoded", "data": [] } }, "docs": "This endpoint creates a draft invoice for a given customer. The invoice remains a draft until you finalize the invoice, which allows you to pay or send the invoice to your customers.
" }, { "info": { "name": "Stripe Post Invoices Invoice", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/invoices/:invoice", "params": [ { "name": "invoice", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Draft invoices are fully editable. Once an invoice is finalized,\nmonetary values, as well as collection_method, become uneditable.
If you would like to stop the Stripe Billing engine from automatically finalizing, reattempting payments on,\nsending reminders for, or automatically reconciling invoices, pass\nauto_advance=false.
Stripe automatically finalizes drafts before sending and attempting payment on invoices. However, if you’d like to finalize a draft invoice manually, you can do so using this method.
" }, { "info": { "name": "Stripe Post Invoices Invoice Lines Line Item Id", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/invoices/:invoice/lines/:line_item_id", "params": [ { "name": "invoice", "value": "", "type": "path", "description": "Invoice ID of line item" }, { "name": "line_item_id", "value": "", "type": "path", "description": "Invoice line item ID" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Updates an invoice’s line item. Some fields, such as tax_amounts, only live on the invoice line item,\nso they can only be updated through this endpoint. Other fields, such as amount, live on both the invoice\nitem and the invoice line item, so updates on this endpoint will propagate to the invoice item as well.\nUpdating an invoice’s line item is only possible before the invoice is finalized.
Marking an invoice as uncollectible is useful for keeping track of bad debts that can be written off for accounting purposes.
" }, { "info": { "name": "Stripe Post Invoices Invoice Pay", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/invoices/:invoice/pay", "params": [ { "name": "invoice", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Stripe automatically creates and then attempts to collect payment on invoices for customers on subscriptions according to your subscriptions settings. However, if you’d like to attempt payment on an invoice out of the normal collection schedule or for some other reason, you can do so.
" }, { "info": { "name": "Stripe Post Invoices Invoice Send", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/invoices/:invoice/send", "params": [ { "name": "invoice", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Stripe will automatically send invoices to customers according to your subscriptions settings. However, if you’d like to manually send an invoice to your customer out of the normal schedule, you can do so. When sending invoices that have already been paid, there will be no reference to the payment in the email.
\n\nRequests made in test-mode result in no emails being sent, despite sending an invoice.sent eve"
},
{
"info": {
"name": "Stripe Post Invoices Invoice Void",
"type": "http"
},
"http": {
"method": "POST",
"url": "https://api.stripe.com/v1/invoices/:invoice/void",
"params": [
{
"name": "invoice",
"value": "",
"type": "path"
}
],
"body": {
"type": "form-urlencoded",
"data": []
}
},
"docs": "
Mark a finalized invoice as void. This cannot be undone. Voiding an invoice is similar to deletion, however it only applies to finalized invoices and maintains a papertrail where the invoice can still be found.
" }, { "info": { "name": "Stripe Post Issuing Authorizations", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/issuing/authorizations/:authorization", "params": [ { "name": "authorization", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Updates the specified Issuing Authorization object by setting the values of the parameters passed. Any parameters not provided will be left unchanged.
[Deprecated] Approves a pending Issuing Authorization object. This request should be made within the timeout window of the real-time authorization flow. \nThis method is deprecated. Instead, respond directly to the webhook request to approve an authorization.
[Deprecated] Declines a pending Issuing Authorization object. This request should be made within the timeout window of the real time authorization flow.\nThis method is deprecated. Instead, respond directly to the webhook request to decline an authorization.
Creates a new Issuing Cardholder object that can be issued cards.
Updates the specified Issuing Cardholder object by setting the values of the parameters passed. Any parameters not provided will be left unchanged.
Creates an Issuing Card object.
Updates the specified Issuing Card object by setting the values of the parameters passed. Any parameters not provided will be left unchanged.
Creates an Issuing Dispute object. Individual pieces of evidence within the evidence object are optional at this point. Stripe only validates that required evidence is present during submission. Refer to Dispute reasons and evidence for more details about evidence requirements.
Updates the specified Issuing Dispute object by setting the values of the parameters passed. Any parameters not provided will be left unchanged. Properties on the evidence object can be unset by passing in an empty string.
Submits an Issuing Dispute to the card network. Stripe validates that all evidence fields required for the dispute’s reason are present. For more details, see Dispute reasons and evidence.
Updates the specified Issuing Settlement object by setting the values of the parameters passed. Any parameters not provided will be left unchanged.
Attempts to update the specified Issuing Token object to the status specified.
Updates the specified Issuing Transaction object by setting the values of the parameters passed. Any parameters not provided will be left unchanged.
To launch the Financial Connections authorization flow, create a Session. The session’s client_secret can be used to launch the flow using Stripe.js.
Disables your access to a Financial Connections Account. You will no longer be able to access data associated with the account (e.g. balances, transactions).
Refreshes the data associated with a Financial Connections Account.
Creates a PaymentIntent object.
\n\nAfter the PaymentIntent is created, attach a payment method and confirm\nto continue the payment. Learn more about the available payment flows\nwith the Payment Intents API.
\n\nWhen you use confirm=true during creation, it’s equivalent to creating\nand confirming the PaymentIntent in the same call. You can use any parameters\navailable in the Updates properties on a PaymentIntent object without confirming.
Depending on which properties you update, you might need to confirm the\nPaymentIntent again. For example, updating the payment_method\nalways requires you to confirm the PaymentIntent again. If you prefer to\nupdate and confirm at the same time, we recommend updating properties through\nthe confirm API instead.
Manually reconcile the remaining amount for a customer_balance PaymentIntent.
You can cancel a PaymentIntent object when it’s in one of these statuses: requires_payment_method, requires_capture, requires_confirmation, requires_action or, in rare cases, processing.
After it’s canceled, no additional charges are made by the PaymentIntent and any operations on the PaymentIntent fail with an error. For PaymentIntents with a Capture the funds of an existing uncaptured PaymentIntent when its status is Uncaptured PaymentIntents are cancelled a set number of days (7 by default) after their creation. Learn more about separate authorization and capture. Confirm that your customer intends to pay with current or provided\npayment method. Upon confirmation, the PaymentIntent will attempt to initiate\na payment.\nIf the selected payment method requires additional authentication steps, the\nPaymentIntent will transition to the Perform an incremental authorization on an eligible\nPaymentIntent. To be eligible, the\nPaymentIntent’s status must be Incremental authorizations attempt to increase the authorized amount on\nyour customer’s card to the ne"
},
{
"info": {
"name": "Stripe Post Payment Intents Verify Microdeposits",
"type": "http"
},
"http": {
"method": "POST",
"url": "https://api.stripe.com/v1/payment_intents/:intent/verify_microdeposits",
"params": [
{
"name": "intent",
"value": "",
"type": "path"
}
],
"body": {
"type": "form-urlencoded",
"data": []
}
},
"docs": " Verifies microdeposits on a PaymentIntent object. Creates a payment link. Updates a payment link. Creates a payment method configuration Update payment method configuration Creates a payment method domain. Updates an existing payment method domain. Some payment methods such as Apple Pay require additional steps to verify a domain. If the requirements weren’t satisfied when the domain was created, the payment method will be inactive on the domain.\nThe payment method doesn’t appear in Elements for this domain until it is active. To activate a payment method on an existing payment method domain, complete the required validation steps specific to the payment method, and then validate the payment method domain with this endpoint. Creates a PaymentMethod object. Read the Stripe.js reference to learn how to create PaymentMethods via Stripe.js. Instead of creating a PaymentMethod directly, we recommend using the PaymentIntents API to accept a payment immediately or the SetupIntent API to collect payment method details ahead of a future payment. Updates a PaymentMethod object. A PaymentMethod must be attached a customer to be updated. Attaches a PaymentMethod object to a Customer. To attach a new PaymentMethod to a customer for future payments, we recommend you use a SetupIntent\nor a PaymentIntent with setup_future_usage.\nThese approaches will perform any necessary steps to set up the PaymentMethod for future payments. Using the Detaches a PaymentMethod object from a Customer. After a PaymentMethod is detached, it can no longer be used for a payment or re-attached to a Customer. To send funds to your own bank account, create a new payout object. Your Stripe balance must cover the payout amount. If it doesn’t, you receive an “Insufficient Funds” error. If your API key is in test mode, money won’t actually be sent, though every other action occurs as if you’re in live mode. If you create a manual payout on a Stripe account that uses multiple payment source types, you need to specify the source type balance that the payout draws fr"
},
{
"info": {
"name": "Stripe Post Payouts",
"type": "http"
},
"http": {
"method": "POST",
"url": "https://api.stripe.com/v1/payouts/:payout",
"params": [
{
"name": "payout",
"value": "",
"type": "path"
}
],
"body": {
"type": "form-urlencoded",
"data": []
}
},
"docs": " Updates the specified payout by setting the values of the parameters you pass. We don’t change parameters that you don’t provide. This request only accepts the metadata as arguments. You can cancel a previously created payout if it hasn’t been paid out yet. Stripe refunds the funds to your available balance. You can’t cancel automatic Stripe payouts. Reverses a payout by debiting the destination bank account. At this time, you can only reverse payouts for connected accounts to US bank accounts. If the payout is in the By requesting a reversal through You can now model subscriptions more flexibly using the Prices API. It replaces the Plans API and is backwards compatible to simplify your migration. Updates the specified plan by setting the values of the parameters passed. Any parameters not provided are left unchanged. By design, you cannot change a plan’s ID, amount, currency, or billing cycle. Creates a new price for an existing product. The price can be recurring or one-time. Updates the specified price by setting the values of the parameters passed. Any parameters not provided are left unchanged.status of requires_ca"
},
{
"info": {
"name": "Stripe Post Payment Intents Capture",
"type": "http"
},
"http": {
"method": "POST",
"url": "https://api.stripe.com/v1/payment_intents/:intent/capture",
"params": [
{
"name": "intent",
"value": "",
"type": "path"
}
],
"body": {
"type": "form-urlencoded",
"data": []
}
},
"docs": "requires_capture.requires_action status and\nsuggest additional actions via next_action. If payment fails,\nthe PaymentIntent transitions to the requires_payment_method status or the\ncanceled st"
},
{
"info": {
"name": "Stripe Post Payment Intents Increment Authorization",
"type": "http"
},
"http": {
"method": "POST",
"url": "https://api.stripe.com/v1/payment_intents/:intent/increment_authorization",
"params": [
{
"name": "intent",
"value": "",
"type": "path"
}
],
"body": {
"type": "form-urlencoded",
"data": []
}
},
"docs": "requires_capture and\nincremental_authorization_supported\nmust be true./v1/payment_methods/:id/attach\nendpoint without fi"
},
{
"info": {
"name": "Stripe Post Payment Methods Detach",
"type": "http"
},
"http": {
"method": "POST",
"url": "https://api.stripe.com/v1/payment_methods/:payment_method/detach",
"params": [
{
"name": "payment_method",
"value": "",
"type": "path"
}
],
"body": {
"type": "form-urlencoded",
"data": []
}
},
"docs": "pending status, use /v1/payouts/:id/cancel instead./v1/payouts/:id/reverse, you confirm that the authorized signatory of the selected bank account authorizes the debit on the bank account and that no other authorization is required.