Use case summary
Search any payment by ID, customer, or card and open a timeline of everything that happened to it: status changes, the route it took, the provider's response, and the callbacks sent to your system. Reconciliation then ties it to the provider's statement. Result: status questions get answered in one place, without logging into provider portals.
- Payment Ops
Why finding one payment takes several portals
When a customer says they paid and the order shows nothing, someone has to find that payment. With several providers, that means guessing which one processed it, logging into its portal, and searching by that provider's reference.
One payment's story is split across systems. The provider's portal holds its response, your system holds the callback, an automatic notification that may not have arrived, and the routing decision sits somewhere else. In the State of Payment Maturity study, 58.5% of companies run payments this way, across unrelated providers and tools with no shared view.
Every question about a payment becomes a small investigation. Support waits on payment operations, payment operations waits on the provider, and a payment that settled days ago can still look pending in your own system.
How to trace a payment from click to settlement
Payment tracking on Corefy starts with one record per transaction, regardless of which provider handled it, and that record is searchable from the dashboard.
- 1
Find the payment
Global search finds any transaction by its ID, the external ID your system assigned to it, the customer, or the card. It works regardless of which provider processed the payment or whether it was created through the API or the dashboard.
- 2
Read its timeline
The transaction timeline lists every status change in order, from the first attempt at a refund or chargeback, alongside the provider's responses at each step.
- 3
See why it failed
Each declined or blocked transaction carries a readable failure reason. When a firewall rule blocks a payment, the record names the specific rule or list that triggered it.
- 4
See which route it took
The routing scheme, the set of rules that decide where each payment goes, shows the exact branch the transaction followed. Revisions record every change made to the scheme, so you can see how the rules looked over time.
- 5
Check what reached your system
Callbacks sent to your system are logged with their content and timing, so you can tell whether a mismatch started with the provider or on your side.
- 6
Confirm the final outcome
Reconciliation, the check of your records against each provider's own statement of processed payments, confirms how each payment actually ended and corrects the record when the statement shows something different. For reports across all providers at once, see unified payment reporting.
What you get
Every question about a single payment is answered from one record, by whoever on the team gets asked.
Faster answers for customers and support
Support and payment operations find the payment, read its timeline, and give the customer a definite answer without waiting on a provider.
Callback problems found in the logs
Callback logs show exactly what your system was sent and when, so engineers can see whether a missing status came from the provider or from the way your system handled it.
Declines you can explain
Each failed payment shows its failure reason and the route it took, so the team can tell a problem with the customer's card apart from a provider or routing problem.
An audit trail for every change
The activity log records who changed what, with username and IP, so changes to routing or settings can be tied to their effect on payments.
Grand Cru Concepts replaced separate provider dashboards with one interface
Before Corefy, Grand Cru Concepts, a software publisher running high-volume consumer products across the US and Canada, managed payments by moving between separate provider dashboards, each with its own routing logic. Over a year after go-live, the team monitors activity, reviews transactions, and coordinates with providers from a single interface for both payments and payouts. Payouts that used to depend on which provider took the original deposit now route across the whole stack, and the approval rate across all active providers stood at 79% as of May 2026.