1. Size & Fit Recommendation
  2. Features
  3. Payments and Refunds
Feature · Payments and Refunds

Payments and Refunds

Distinguish provider capture from authorization and reduce collected cash only after a verified refund outcome.

OverviewVerified Payment Evidence
Size & Fit Recommendation · Payments and Refunds

Verified Payment Evidence

Payment evidence

New
IdParentTypeAmount USDOccurred atProvider event ID
IDD-197SO-59314Authorization77017 OctPEI-426
IDD-220SO-22728Capture11010 OctPEI-700
IDD-390SO-65917Refund64027 OctPEI-643
IDD-445SO-26255Void93012 OctPEI-234
IDD-662SO-36681Authorization3017 OctPEI-878
6 of 6 records
IDD-197Payment evidence · PE-15780
Authorization
ParentSO-59314
Amount USD770
Occurred at17 Oct
Provider event IDPEI-426
Provider referencePR-978
Example screen with sample data

What you can do

Read the provider outcome behind the amount

Payment evidence identifies the provider event and reference, its type, amount and date. Authorization, Capture, Refund and Void describe different provider outcomes. Commerce Operator and Commerce Reviewer use the verified evidence to understand what happened to the order’s payment request.

Captured cash comes from verified capture evidence. A refund reduces that amount only after the provider outcome is verified and recorded. The order’s accepted state or a customer’s returned garment does not by itself establish either cash event. Operations Overview brings captured and net collected payment evidence into the wider review of pending decisions and exceptions.

How the work is organized

  • Payment evidence. Retain the provider event identifier and reference with the order. Review whether the evidence is verified before using the amount in the collected-payment discussion.
  • Refund decision. Commerce Reviewer independently approves the selected refund scope against the order version and relevant evidence. The request then follows the provider action using its stable identity.
  • Unknown outcomes. An uncertain provider response remains pending reconciliation. Read the existing result and authoritative references before deciding whether a further request is necessary.

What to agree during setup

Configure the payment provider and agree how its authorization, capture, refund and void events reach the order. Define which evidence establishes verification and who investigates duplicate or conflicting event identifiers. Keep the provider reference available for the person reconciling the result.

Agree the refund policy and the amount under review using captured and earlier refunded evidence. Decide how returned product information contributes to the decision without treating a physical return as a cash refund. Establish the handoff when a provider outcome is unknown so the team does not reduce collected cash or send a second request prematurely.

Check the handoff on an actual case

An apparel order has been accepted and its provider authorization is recorded. Commerce Operator checks for the verified capture before treating the payment as collected. The event’s provider reference ties the amount to the correct order and distinguishes it from an unrelated customer transaction.

In this rehearsal, the order has a verified $120 capture and the customer requests a $30 refund. Commerce Reviewer checks the order, current version and requested amount, then records the independent decision. Net collected payment evidence remains $120 while the refund outcome is unknown. Once the $30 refund is verified, it becomes $90. Keep the earlier authorization out of that calculation and count each provider event once.

Rehearse an interrupted response after the refund request. The operation remains pending reconciliation while the reviewer reads the existing provider result. If the refund already took effect, the team should confirm that outcome rather than issue it again. If the reference or amount does not match, retain the discrepancy for review and keep the uncertain amount out of a claimed completed refund.

What your team sees

  • Verified Payment Evidence — Confirmed provider events retain their type, amount and external identity.
  • Refund Review Queue — Orders in refund review provide the current amount and captured/refunded context.
  • Receipt Exceptions — Incomplete or disputed actions identify the result that needs reconciliation.

Follow the work through

What it keeps track of

Data model
Payment evidence
Verified provider authorization, capture, refund and void events
Sales orders
Priced sales orders carrying fit recommendation scope
Review decisions
Independent review decisions on submitted revisions
Operation receipts
Stable operation keys and persisted effect results
Record attachments
Evidence files attached to operational records

Who uses it

Permissions
Commerce Operator
Supplies the order context and requests eligible actions.
Commerce Reviewer
Approves refunds and reconciles uncertain outcomes.
Auditor
Follows authorized payment and review evidence.

Set up Size & Fit Recommendation your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started