Enhanced charge history Early Adopter Program
Enhanced charge history provides a charge status timeline inside the merchant portal allowing you to easily see what affected the charge and troubleshoot charge errors.
This article provides an overview of what is covered by the enhanced charge history and the activity types that are recorded when something changes a charge.
Enhanced charge history overview
Enhanced charge history provides a list of activities that affected the charge and in case of errors, an actionable message with next steps. Each activity includes more detailed information when clicking on the activity title. The details shown will depend on the type of activity.
Charge timeline
Access the Charge timeline on the Order details page in the charge details section, or on the Charge details page. This timeline consists of a series of activities that impacted the charge. Each activity has a description of the action taken on the charge, and in case of errors, a suggested solution. Some messages include links to documentation that covers the situation in more detail.
Additional details
Additional details for activities will be available by clicking on the activity title in the charge status timeline. Clicking the activity title will bring up a modal with more information on the activity such as charge amount, error codes, and messages in case of charge errors.
Charge status
Enhanced charge history also displays the latest activity alongside the order status on the Customer details page. The modal with more details is also available from this view.
Activity type availability and timeline
The following table displays all activities and what triggers the activity to be recorded.
Released
Activity |
When activity is recorded |
|
Created (July 24) |
A charge is created. |
|
Payment failure (July 24) |
There was a problem charging the customer |
|
Payment success (July 24) |
An order was successfully charged |
|
Inventory failure (July 24) |
There is not enough inventory to fulfill the order. |
|
Payment attempt initiated (July 28) |
Billing is triggered and payment is attempted via SEPA. |
|
Payment attempt challenged (July 28) |
A payment is blocked by 3DSecure and requires the customer to accept the payment. |
|
Card updated now pending next attempt (August 1) |
The customer updated their payment method, while in Dunning, and the charge is queued up again for processing. |
|
Max retries reached (August 4) |
When Recharge stops trying a failed payment. This depends on the Dunning rules configured for charges. |
|
Variant error (August 8) |
The processing of an order failed because the variant has been deleted from Shopify. |
|
Refund success (August 17) |
Refund was processed successfully. |
|
Credit applied (August 22) |
Credits were used to pay for (part of) an order. |
|
Credit refunded (August 22) |
Credits were refunded due to a processing error. |
|
Refund initiated (September 12) |
A refund was triggered for SEPA payments. |
|
Refund failure (September 12) |
Something went wrong refunding the customer. |
Planned for release
Activity |
When activity is recorded |
|
Skipped |
A scheduled charge is skipped, by the customer or the merchant. |
|
Rescheduled |
A scheduled charge is rescheduled, by the customer or the merchant. |
|
Order submission failure |
An order failed to get created for stores on Recharge Checkout on Shopify and BigCommerce. |
|
Order submission success |
An order was successfully created in BigCommerce or Shopify for stores using the Recharge Checkout. |
