Marketplaces
Many checkouts, one readable outcome per run.
Marketplaces hit every wall at once: buyers on many checkouts, methods gated per checkout, and fraud scoring that differs by card. The extension reads each run and reports the gateway's own values.
What changes
- Per-checkout switches
- Fraud options dropped
- Site and plan decoded
- Outcome attributable per run
Acceptance is not one number
A marketplace with a high overall acceptance rate can still be losing a third of its volume on one checkout because of one issuer. An aggregate hides exactly the segment that needs attention.
The extension records each run by status, decline code, ACS vendor and charge id, so a failure has an address before it becomes a quarter.
Switches have to be scoped
A bypass that is right for one checkout can be wrong for another. Each switch writes straight to storage, so the behaviour can be enabled deliberately instead of globally on day one.
Auto-run, 3DS, blacklist, fraud, decline retry, deny path, forced ACS failure and logging can each be judged on its own run.
Reconciliation cannot be approximate
When a run settles, the card is posted with the site and plan decoded from the checkout link. That makes the posted record name the checkout it came from rather than a generic label.
Every settled run carries its charge id beside the relay response, which is what makes the report usable rather than indicative.