Scenario

Marketplace split refunds and seller chargebacks

Two-sided marketplace on Stripe Connect, where a buyer refund has to claw money back from the seller and possibly from the platform fee at the same time.

Reference numbers

What the math looks like in this pattern.

Illustrative pause window

7 days

Illustrative
Before Axiru

The pain we hear about over and over in this pattern.

Configuration

How Axiru is set up for this pattern.

These are the policies a finance or ops team would typically enable on day one. Thresholds shown are illustrative; you tune them to your own materiality.

Seller chargeback velocity

payouts

If a connected account accumulates three or more chargebacks in a rolling seven-day window, payouts are paused and the trust team is alerted.

Platform-vs-seller refund attribution

refunds

Every refund decision is tagged with funding source (platform, seller, split) and surfaced in the audit log.

High-value buyer refund pre-check

refunds

Refunds above an illustrative $1,000 threshold check seller payout balance first and warn if the clawback would put the seller negative.

Signals to watch

What you should be measuring once this is running.

What good looks like

The steady state if the configuration is doing its job.

Framing

Pausing a seller used to be a Slack-message-plus-DM ritual. Now the policy fires, the seller gets a templated email, the trust queue picks it up.

Common operating pattern in Stripe Connect marketplaces
Next step

Run the marketplace split refunds and seller chargebacks simulation on your own data.

Upload 90 days of refund history. Axiru replays these policies in shadow mode. Nothing actually blocks any money until you flip the switch.

Start in shadow mode first. Move to live enforcement later.

Marketplace split refunds and seller chargebacks | Axiru scenario | Axiru