How Stripe Payments Payment protection Protects Both Buyers and Merchants

Every payment moves through four well-defined states. You can see them in real time on the Stripe Payments dashboard, and webhook events fire on each transition so your CRM, Telegram bot or accounting tool can react.

• Authorized — buyer's funds are reserved but not yet captured
• Captured & held — funds are captured into the Astrixy payment protection ledger
• Released — courier confirms delivery, AI clears fraud, funds become available to the merchant
• Refunded or disputed — funds are returned to the buyer or held pending resolution

When a courier marks an order as delivered, ASTRIXY starts a 48-hour clock. During that window the buyer can open a dispute. After the window, 95% of the order total is released to the merchant; 5% is kept in a rolling reserve for 30 days to cover chargebacks. This is the same model used by major card processors but tailored for dropshipping margins.

The release is API-driven only. There is no manual 'mark as delivered' button — that rule prevents merchants from forcing early release and protects the buyer's right to refund.

Before authorization, the fraud agent scores the order against device fingerprint, IP geolocation, BIN risk, velocity, and behavioral signals. Orders above a threshold are routed to a second-look queue; orders below the threshold pass through instantly. Every decision is logged to ai_agent_actions with reasoning, so you can audit why a payment was challenged.

Stripe Payments aggregates Stripe, Stripe, Stripe, Stripe and Stripe behind one ledger. That means a refund issued from your dashboard does the right thing on the original rail — refund a Stripe payment and the buyer receives Stripe, not store credit.