These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Auction Platform
- Features
- Payments and refunds
Payments and refunds
Review payment state and approved returns against each sale.
OverviewPending Refund Approval×
Auction Platform · Payments and refunds
New
Pending Refund Approval
Approval conditions
| Refund number | Sale order | Amount | Reason | Approved by | Requested at | |
|---|---|---|---|---|---|---|
| SR-76592 | SO-46187 | 160 | Bidder | 13 Oct | ||
| SR-11616 | SO-79926 | 550 | Defective | 24 Oct | ||
| SR-55556 | SO-77988 | 250 | Damaged | 09 Oct | ||
| SR-42808 | SO-24833 | 900 | Wrong item | 05 Oct | ||
| SR-52649 | SO-84388 | 710 | Fraud | 20 Oct |
6 of 6 records
SO-46187Settlement refunds · SR-76592
BidderAmount160
Requested at13 Oct
StatusPending
What you can do
Keep the operating record clear
A customer requests money back after a damaged delivery. Service records a refund amount, reason and order link. Merchant Owner reviews the pending request against the amount that can still be returned. The refund processing state and provider reference help finance reconcile the request with the actual payment record.
Merchant Owner reviews a pending refund against the sale order, successful payment records and earlier refunds. Customer Service Rep records the shopper reason and follows a failed or processing refund. A local authorization or capture row is reconciled with its provider result before staff treat money as received or returned.
How the work is organized
- Payment. Read the payment kind and status alongside the order financial state and amount paid.
- Request. Keep the refund amount, reason and sale order together before seeking approval.
- Outcome. Compare prior refunds with the remaining refundable amount and reconcile the provider reference after processing.
What to agree during setup
Agree who approves refunds and what amount ceiling applies to customer service. Keep payment method configuration separate from a successful provider charge. Set up payment acquiring before relying on a local authorization or capture record as money received. Decide how failed refunds are retried and explained to the shopper.
During the pilot, assign the exception owner and record the decision on the related order or catalog. Check the next handoff against the saved status, date and linked records before more staff start using the process.
Check the handoff on an actual case
Start with a paid order, inspect its successful payment and requested refund, then check that the approver is recorded. Compare the refund amount to money paid less prior refunds. Follow one successful and one failed refund so the team knows which case needs provider reconciliation.
Use the same case to rehearse access. Have the next owner explain the saved record, perform the permitted action and show the resulting status to the following owner. Correct a broken handoff before expanding the pilot.
What your team sees
- Pending Refund Approval — Shows the cases and current status for this module’s owner.
- Refund Processing — Separates cases that need a second check or decision.
Follow the work through
See the operating process for the connected handoff. Implementation gives the pilot sequence, and roles sets access before people start editing records.
What it keeps track of
Data model- Settlement payments
- Records a payment for an order, so finance can track processing status and risk.
- Settlement refunds
- Tracks a refund issued to a bidder, so finance can reconcile returns and payouts.
- Sale orders
- Represents a completed purchase, tracking payment, fulfilment, and status for the team.
- Payment methods
- Defines a payment option offered at checkout, like card or bank transfer, for finance to manage.
- Config validation runs
- Checkout configuration validation runs produced by the Pricing, tax, shipping, payment workflow. One row per validated configuration set; validation never mutates the merchant configuration.
Who uses it
Permissions- Merchant Owner
- Makes the refund decision and maintains payment methods.
- Customer Service Rep
- Prepares the case and follows its processing outcome.
Set up Auction Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.