Refunds & disputes

Card-rail exception handling. Wire transfers have no chargeback path - once a bank transfer settles against a proforma, reversals are an operational matter outside the card dispute system. This page is for card payments.

Refunds

Merchant-initiated refunds reverse a settled card payment. Outpost issues a refund invoice for the reversal - you can retrieve it by Outpost refund ID or PSP reference (see API map below and Invoicing).

Creating a refund via API is documented today on the Stripe Billing integration (POST /api/payments/{paymentId}/refund). For card setups on Stripe, Adyen, or Pagar.me that use your existing checkout, follow the refund path agreed for that PSP connection - the refund invoice lookup endpoints above still apply once the refund exists.

Chargebacks & disputes

Chargebacks and disputes are initiated by the cardholder or issuer through the PSP. Outpost does not yet expose a dedicated public webhook catalog for dispute lifecycle events (for example, returns and mandate disputes are not announced as first-class events on the Stripe Billing path either).

In practice today: monitor disputes in the PSP dashboard (and any ops channel Outpost provides for your account), and treat settlement / invoice records in Outpost as the source of truth for what was collected and refunded. When dedicated dispute events ship, they will appear in the API reference event catalog.

API map

Invoice lookup schemas live under Invoices. Creating a refund via API is documented on the Stripe Billing path today - see the integration guide for how it fits the Billing flow.

• GET/api/refunds/{refundId}/invoice
• GET/api/refunds/invoice?psp_reference={psp_reference}
• POST/api/payments/{paymentId}/refund