Corrily home pagelight logo
Charges
Update charge
POST

/v1/charges/{user_id}/{origin}/{origin_id}

X-Api-Key*
curl --request POST \
  --url https://client.corrily.com/v1/charges/{user_id}/{origin}/{origin_id} \
  --header 'X-Api-Key: <x-api-key>'
curl --request POST \
     --url https://client.corrily.com/v1/charges/user_id/origin/origin_id \
     --header 'Content-Type: application/json'

​
Path Params

originrequired
string

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

origin_idrequired
string

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

user_idrequired
string

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

​
Body Params

amount
float

The amount (price) of the charge.

created
integer

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.

metadata
object

Free form key-value data. Metadata is useful for storing additional, structured information for a charge.