Charges
Learn about what a charge is, how it's created, and how captures, cancels, and refunds work
A charge represents a payment authorization. The charge creation process is handled by Digital River. Throughout a charge's lifecycle, the object can contain one or more captures, cancels, and refunds.
How a charge is created
Whether you're using Low-code checkouts or Direct Integrations, the payment authorization process remains the same.
At the time of order creation, Digital River creates a charge whose amount is equal to the associated source's amount and then submits an authorization request that gets routed to the appropriate payment provider.
For example, as you build a Direct Integrations' checkout, customers might provide credit card information during the payment collection stage. This information is then used to create a primary source that you associate with the checkout. After you convert the checkout to an order, Digital River creates a charge and then sends an authorization request to a payment processor who forwards it to a payment provider. If the request is approved by the provider, Digital River moves the charge's state to capturable and creates an event with a type of order.charge.capturable.
Once a provider authorizes payment, the charge on a credit card typically remains capturable for seven days.
A charge's amount represents the initial authorization on a customer's payment method. But it's ultimately all the captures, cancellations, and refunds during an order's lifecycle that determines how much a customer pays.
How captures, cancels, and refunds work
An order's payment.charges[] contains an enduring record of all the captures[], cancels[], and refunds[] that occur during that order's lifecycle.
All captures, cancels, and refunds have an initial state of pending and then either transition to complete or failed. With each of these state transitions, a corresponding event is created.
For example, when you initiate the payment cancellation process, Digital River creates an event with a type of order.charge.cancel.pending, followed either by order.charge.cancel.complete or order.charge.cancel.failed.
During an order's lifecycle, an order's totalAmount and each of its payment.charges[].amount(s) remain unaltered. The actual amount a payment method is debited or credited is reflected by capturedAmount and refundedAmount, respectively.
Captures
A capture represents the settling of an authorization. In other words, how much a customer's payment method is debited. Some payment methods require that a charge's full amount be captured all at once, while others permit multiple captures.
When a POST/ fulfillments that specifies an items[].quantity is submitted, Digital River attempts to capture payment.
For more details, refer to the Capturing and cancelling payment charges page.
The following POST /fulfillments seeks to partially capture payment on an order.
Once submitted, you can be notified that the capture process has begun by listening for the event with a type of order.charge.capture.pending.
In the above example, the POST /fulfillments informed our payment services that two line items were fulfilled. As a result, the order contains two captures[], each with a unique id and a captured amount. As more goods are fulfilled, and you respond by submitting additional POST /fulfillments, an order's capturedAmount provides a running total of how much has been settled.
In this example, since the order's primary payment source has a type of creditCard, each captures[] will (typically) briefly transition to a state of pending before becoming complete. Once a capture moves into this state, Digital River creates order.charge.capture.complete.
Cancels
A cancel negates all or part of a payment authorization. Cancels don't result in the debiting or crediting of a customer's payment method. That same underlying payment method determines whether a charge can be partially cancelled or only supports full cancellations.
When you send a POST /fulfillments that specifies an items[].cancelQuantity, Digital River attempts to cancel payment.
For more details, refer to the Capturing and cancelling payment charges page.
Once submitted, you can be notified that the cancellation process has begun by listening for the order.charge.cancel.pending.
In the above example, the POST /fulfillments informed our payment services that two line items were cancelled. As a result, the order contains two cancels[], each with a unique id and a cancelled amount.
In this particular example, since all of the order's charges[] are either captured or cancelled, the order's state moves to complete and order.complete is created.
Refunds
In an order, a charges[].refunds[] represents a partial or full reversal of a charges[].captures[].
A charges[].refunds[] however is not the same object as a refund created by a POST /refunds request. This is because, for batch processing purposes, Digital River often aggregates numerous of these refunds into a lesser number of charges[].refunds[].
For details on how to create refunds, refer to the Issuing refunds page.
The following GET /refunds request is searching for all the refunds created on an order.
In this particular example, two POST /refunds were submitted, resulting in the creation of two refunds, each of which is represented by an element in data[]. You can see that Digital River has aggregated the amount of those unique objects into a single charges[].refunds[].amount.
By retrieving the charge, you can access the unique id of this refunds[], which is different from the id of each refund.
Handling charge failures
When a payment authorization request is unsuccessful, the charge's state becomes failed. The same is true for failed captures, cancels, and refunds.
Each of these objects contains a failureMessage and failureCode that you may be able to use to pinpoint a reason for the failure.
For more information, refer to authorization declines and handling rejected orders.
The charge lifecycle
A charge's state can be pending, capturable, processing, complete, cancelled, or failed.
When a charge's state changes, Digital River creates a corresponding event. For example, when the charge's state changes from pending to capturable an event with a type of order.charge.capturable is created.
The state values for a successful charge (i.e. the happy path) are pending > capturable > processing > complete .
The following table lists the possible states of a charge and their corresponding events:
| 1) When the charge... | (2) its state transitions to... | (3) and an...event is emitted. |
|---|---|---|
...is awaiting authorization, typically because additional customer action is required |
|
|
...is authorized by the payment provider |
|
|
...is being processed by the payment provider |
|
|
...is captured in full (or captured in part with the remainder cancelled) and there are no pending charge operations. |
|
|
...is cancelled in full and there are no pending charge operations. |
|
|
fails to authorize |
|
|
For different success and error scenarios, you can create tests to determine whether your integration returns the expected state value.
Last updated