Test mode: Return an OutboundPayment
Transitions a test mode created OutboundPayment to the returned status. The OutboundPayment must already be in the processing state.
Path parameters
Response
Successful response.
Amount (in cents) transferred.
Returns true if the object can be canceled, and false otherwise.
Time at which the object was created. Measured in seconds since the Unix epoch.
Three-letter ISO currency code, in lowercase. Must be a supported currency.
ID of the customer to whom an OutboundPayment is sent.
An arbitrary string attached to the object. Often useful for displaying to users.
The PaymentMethod via which an OutboundPayment is sent. This field can be empty if the OutboundPayment was created using destination_payment_method_data.
The date when funds are expected to arrive in the destination account.
The FinancialAccount that funds were pulled from.
A hosted transaction receipt URL that is provided when money movement is considered regulated under Stripe's money transmission licenses.
Unique identifier for the object.
If the object exists in live mode, the value is true. If the object exists in test mode, the value is false.
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.
String representing the object's type. Objects of the same type share the same value.
The description that appears on the receiving end for an OutboundPayment (for example, bank statement for external bank transfer).
Current status of the OutboundPayment: processing, failed, posted, returned, canceled. An OutboundPayment is processing if it has been created and is pending. The status changes to posted once the OutboundPayment has been "confirmed" and funds have left the account, or to failed or canceled. If an OutboundPayment fails to arrive at its destination, its status will change to returned.