> ## Documentation Index
> Fetch the complete documentation index at: https://docs.corrily.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Update charge

<RequestExample>
  ```bash Bash theme={null}
  curl --request POST \
       --url https://client.corrily.com/v1/charges/user_id/origin/origin_id \
       --header 'Content-Type: application/json'
  ```
</RequestExample>

## Path Params

<ParamField path="origin" type="string" required>
  The payment gateway that handled the charge. Accepted values: `stripe`,
  `paypal`, `chargebee`.
</ParamField>

<ParamField path="origin_id" type="string" required>
  A unique identifier for the charge. This can be the ID that the payment
  gateway assigned to the charge.
</ParamField>

<ParamField path="user_id" type="string" required>
  The [User ID](/api-reference/users/user-id) that you provided when you
  [created the charge](/api-reference/charges/create-charge).
</ParamField>

## Body Params

<ParamField body="amount" type="float">
  The amount (price) of the charge.
</ParamField>

<ParamField body="created" type="integer">
  A 10-digit (seconds) [UNIX timestamp](https://en.wikipedia.org/wiki/Unix_time)
  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.
</ParamField>

<ParamField body="currency" type="string">
  The three-letter [(ISO
  4217\)](https://en.wikipedia.org/wiki/ISO_4217#Active_codes) currency code.
</ParamField>

<ParamField body="status" type="string">
  The status of the charge. Accepted values: `pending`, `succeeded`, `failed`.
</ParamField>

<ParamField body="metadata" type="object">
  Free form key-value data. Metadata is useful for storing additional, structured information for a charge.
</ParamField>