Card network rules and local regulatory requirements are different for in-person payments. If you accept payments using Stripe Terminal, you must provide customers with the option to receive a physical or email receipt. Stripe provides everything you need to start offering receipts with your first transaction.
Receipts must contain certain fields to comply with card network rules. You can use Stripe’s prebuilt email receipts, or use receipt data from the Stripe API and your Terminal integration to generate on-brand custom receipts.
Prebuilt email receipts
Prebuilt email receipts already include all card network-required fields. It’s the simplest way to set up compliant receipts.
If you have the customer’s email, use the
receipt_email field when creating a PaymentIntent. When you provide a
receipt_email, Stripe automatically emails a compliant receipt to the customer when capturing the PaymentIntent.
To trigger an automatic email receipt after the customer checks out, update the PaymentIntent’s
receipt_email with the customer’s email.
For more information about automatic email receipts, see Email Receipts.
You can also customize receipts to include any design and content you want—as long as you list required information. When you accept in-person payments with EMV chip cards, card networks require you to include several fields on the receipts you provide to customers.
The Stripe API allows you to fetch necessary fields for compliance-ready receipts.
The following fields become available in the PaymentIntent object as soon as the payment is confirmed.
|Required (Optional in US)
Whether you’re emailing or printing your custom receipts for Terminal payments, be sure to include the required fields to meet card network rules.