Refunds
Give money back on purpose.
A refund is a payment in reverse, and it deserves the same care.
Set a policy, and the
exceptions go to a person.
How a refund runs
What you keep afterwards
Disputes
A real lifecycle, in place of an inbox.
A dispute arrives, a clock starts, and a decision has to be made.
The product carries
that shape rather than leaving it to email.
It arrives
A dispute lands on the case list with the payment it belongs to.
You gather
Evidence templates ask for the things that usually decide a case.
You choose
Defend it, accept it, or escalate it. Each path is its own action.
It settles
The outcome lands on the case and on your balance together.
Instant bank rails have their own return mechanism, and the product carries that one as its own case type rather than pretending it behaves like a card.
Watching the numbers
Know the ratio before somebody else tells you.
Card networks watch how often a business gets disputed.
Watching it yourself is the
whole point of a monitoring screen.
MONITORING
The rate, over time
Where you sit, and which way the line is moving.
EARLY WARNING
Alerts before a case
Some disputes announce themselves first, and that is a chance to act.
RISK
Rules, reviews and a blocklist
Patterns you describe get raised to a person who decides.
See a dispute from arrival to outcome.
Thirty minutes. We open a case, gather the evidence and follow it to settlement.
hello@orchespay.com