Update charge

post

https://client.corrily.com/v1/charges/{user_id}/{origin}/{origin_id}

Update a single charge from a single customer.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

🚧
Custom payment gateway integrations only
You do not need to use this endpoint if you have granted Corrily automated access to your payment gateway's subscription and charge events.

Path Params

origin

string

required

The payment gateway that handled the charge. Accepted values: stripe, paypal, chargebee

origin_id

string

required

A unique identifier for the charge. This can be the ID that the payment gateway assigned to the charge.

user_id

string

required

The User ID that you provided when you created the charge.

Body Params

amount

float

The amount (price) of the charge.

created

int32

A 10-digit (seconds) UNIX timestamp indicating when the charge was created. This timestamp should represent when the charge was initialized, regardless of the status of the charge during the initialization. It's rare to need to update created after initially setting it.

currency

string

The three-letter (ISO 4217) currency code.

status

string

The status of the charge. Accepted values: pending, succeeded, failed

Headers

X-Api-Key

string

required

Your organization's API key.

Language

Loading…

Response

Click Try It! to start a request and see the response here!

🚧Custom payment gateway integrations only

🚧
Custom payment gateway integrations only