Returns a list of PaymentMethods for a given Customer
" }, { "info": { "name": "Stripe Get Customers Customer Payment Methods Payment Method", "type": "http" }, "http": { "method": "GET", "url": "https://api.stripe.com/v1/customers/:customer/payment_methods/:payment_method", "params": [ { "name": "customer", "value": "", "type": "path" }, { "name": "expand", "value": "", "type": "query", "description": "Specifies which fields in the response should be expanded." }, { "name": "payment_method", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Retrieves a PaymentMethod object for a given Customer.
" }, { "info": { "name": "Stripe Get Payment Intents", "type": "http" }, "http": { "method": "GET", "url": "https://api.stripe.com/v1/payment_intents", "params": [ { "name": "created", "value": "", "type": "query", "description": "A filter on the list, based on the object `created` field. The value can be a string with an integer Unix timestamp or a dictionary with a number of different query options." }, { "name": "customer", "value": "", "type": "query", "description": "Only return PaymentIntents for the customer that this customer ID specifies." }, { "name": "ending_before", "value": "", "type": "query", "description": "A cursor for use in pagination. `ending_before` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with `obj_bar`, your subsequent call can include `ending_before=obj_bar` in order to fetch the previous page of the list." }, { "name": "expand", "value": "", "type": "query", "description": "Specifies which fields in the response should be expanded." }, { "name": "limit", "value": "", "type": "query", "description": "A limit on the number of objects to be returned. Limit can range between 1 and 100, and the default is 10." }, { "name": "starting_after", "value": "", "type": "query", "description": "A cursor for use in pagination. `starting_after` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with `obj_foo`, your subsequent call can include `starting_after=obj_foo` in order to fetch the next page of the list." } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Returns a list of PaymentIntents.
" }, { "info": { "name": "Stripe Post Payment Intents", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/payment_intents", "body": { "type": "form-urlencoded", "data": [] } }, "docs": "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 Search for PaymentIntents you’ve previously created using Stripe’s Search Query Language.\nDon’t use search in read-after-write flows where strict consistency is necessary. Under normal operating\nconditions, data is searchable in less than a minute. Occasionally, propagation of new or updated data can be up\nto an hour behind during outages. Search functionality is not available to merchants in India.
Retrieves the details of a PaymentIntent that has previously been created.
\n\nYou can retrieve a PaymentIntent client-side using a publishable key when the client_secret is in the query string.
If you retrieve a PaymentIntent with a publishable key, it only returns a subset of properties. Refer to the payment intent object reference for more details.
" }, { "info": { "name": "Stripe Post Payment Intents", "type": "http" }, "http": { "method": "POST", "url": "https://api.stripe.com/v1/payment_intents/:intent", "params": [ { "name": "intent", "value": "", "type": "path" } ], "body": { "type": "form-urlencoded", "data": [] } }, "docs": "Updates properties on a PaymentIntent object without confirming.
\n\nDepending 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. Returns a list of your payment links. Creates a payment link. Retrieve a payment link. Updates a payment link. When retrieving a payment link, there is an includable line_items property containing the first handful of those items. There is also a URL where you can retrieve the full (paginated) list of line items. List payment method configurations Creates a payment method configuration Retrieve payment method configuration Update payment method configuration Lists the details of existing payment method domains. Creates a payment method domain. Retrieves the details of an existing 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. Returns a list of PaymentMethods for Treasury flows. If you want to list the PaymentMethods attached to a Customer for payments, you should use the List a Customer’s PaymentMethods API instead. 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. Retrieves a PaymentMethod object attached to the StripeAccount. To retrieve a payment method attached to a Customer, you should use Retrieve a Customer’s PaymentMethods 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.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": "