การจัดการเงินคืนและข้อพิพาท

Charging customers is only half the job. A smooth refund process builds trust, meets legal obligations, and reduces costly chargebacks. Stripe makes refunds a single API call.

To refund, you need the original PaymentIntent or charge ID. Store it on your order record at purchase time so you can look it up later.

Create a refund by passing the PaymentIntent. With no amount, Stripe refunds the full charge.

To refund part of a payment, pass an amount in the smallest currency unit (cents).

Tag refunds with a reason for your records and Stripe's analytics. Valid values include requested_by_customer, duplicate, and fraudulent.

Reflect the refund in your own system so the order status is accurate and the customer cannot use a refunded product.

Refunds can also be issued from the Stripe Dashboard. Listen for the charge.refunded webhook so your database stays in sync no matter where the refund originates.

A dispute (chargeback) happens when a customer asks their bank to reverse a charge. Stripe withdraws the funds and a dispute fee, then asks you for evidence.

Listen for charge.dispute.created and submit evidence — receipts, delivery proof, customer communication — to contest it.

The best defense is prevention:

• Use a clear billing descriptor
• Send receipts immediately
• Offer easy self-serve refunds
• Keep records of every transaction

Handle money responsibly:

• Store the PaymentIntent on each order
• Support full and partial refunds with reasons
• Sync via the charge.refunded webhook
• Contest disputes with evidence and prevent them upfront

You completed the payment lifecycle:

• Store the PaymentIntent to enable refunds
• Issue full or partial refunds with a reason
• Sync via the charge.refunded webhook
• Respond to disputes with evidence and prevent chargebacks

Your one-time payment flow now handles money end to end.