POST /v1/payment_records/{id}/report_payment_attempt_informational
Report informational updates on the specified Payment Record.
Servers
- https://api.stripe.com/
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
id |
String | Yes |
The ID of the Payment Record. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/x-www-form-urlencoded" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
description |
No |
An arbitrary string attached to the object. Often useful for displaying to users. |
|
customer_details |
Object | No |
Customer information for this payment. |
customer_details.customer |
String | No | |
customer_details.email |
String | No | |
customer_details.name |
String | No | |
customer_details.phone |
String | No | |
expand[] |
Array | No |
Specifies which fields in the response should be expanded. |
metadata |
No |
Set of key-value pairs that you can attach to an object. This can be useful for storing additional information about the object in a structured format. Individual keys can be unset by posting an empty value to them. All keys can be unset by posting an empty value to |
|
shipping_details |
No |
Shipping information for this payment. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.