Collect tips

Terminal enables you to collect voluntary tips in two ways:

On-receipt tipping – Tips are collected when the payment is captured. This method is most commonly used when collecting tips on printed paper receipts.
On-reader tipping – The card reader suggests tips to customers before collecting payment.

For mandatory tips, you must include the tip amount in the original PaymentIntent amount. You can’t use on-receipt or on-reader tipping.

On-receipt vs. on-reader tipping

The table below outlines some differences between on-receipt tipping and on-reader tipping.

To use the on-reader tipping feature on your BBPOS WisePad 3, you must request access to the beta by contacting stripe-terminal-betas@stripe.com.

	On-reader tipping	On-receipt tipping
Country	BBPOS WisePad 3: Beta Available in: BBPOS WisePOS E: Available in:
Reader	BBPOS WisePad 3 BBPOS WisePOS E	Any
Integrations/SDKs	BBPOS WisePad 3: Android SDK iOS SDK BBPOS WisePOS E: All SDKs (JS, iOS, Android), server-driven	All SDKs (JS, iOS, Android), server-driven
Merchant category	Any	Restricted
Card brand	Any	Visa, Mastercard, American Express, Discover
Tipping limit	Maximum charge amount for the total amount inclusive of the tip, which is eight or nine digits depending on the currency	Maximum charge amount for the total amount inclusive of the tip
Customer experience	Tips suggested on the reader	Tips set with custom integration on the point of sale or on a paper receipt
Customer credit card statement	Shows the payment amount inclusive of the tip, without waiting for settlement	Shows an initial pending authorization that’s later updated to reflect the initial amount inclusive of the tip

How tips are displayed on-receipt or on-reader

On-receipt and on-reader tipping use the PaymentIntents API, work with all Terminal SDKs (JS, iOS, Android) and server-driven integrations, and require manual capture.

Choose only one tipping method per PaymentIntent. If you use on-reader tipping, the same PaymentIntent can’t be used for on-receipt tipping.

The table below summarizes the specific API behavior.

On-reader tipping On-receipt tipping

Tips in the API request The reader automatically adds the customer-selected tip when processing a payment. You add the tip amount and pass the total amount_to_capture when capturing a PaymentIntent. The amount_to_capture field is inclusive of the tip.

Tips and API response amount The amount_details object appears in the API response when processing a payment. The tip amount is returned in the amount_details object. Tips are not directly represented but can be derived from the Charge object. The amount in the PaymentIntent capture response is inclusive of the tip.

	On-reader tipping	On-receipt tipping
Tips in the API request	The reader automatically adds the customer-selected tip when processing a payment.	You add the tip amount and pass the total amount_to_capture when capturing a PaymentIntent. The `amount_to_capture` field is inclusive of the tip.
Tips and API response amount	The amount_details object appears in the API response when processing a payment. The tip amount is returned in the `amount_details` object.	Tips are not directly represented but can be derived from the Charge object. The `amount` in the `PaymentIntent` capture response is inclusive of the tip.
Tips in the underlying `Charge` object	Tips are not directly represented in the `Charge` object. After capture, the fields below all show the same value inclusive of the tip. amount amount_authorized amount_captured	Tips can be derived from the `Charge` object. You can derive the tip by subtracting `amount_authorized` from `amount`. `amount_authorized` is the original authorized amount exclusive of the tip. `amount_captured` and `amount` are the same and both are inclusive of the tip.

Tips in the underlying Charge object

Tips are not directly represented in the Charge object.

After capture, the fields below all show the same value inclusive of the tip.

Tips can be derived from the Charge object. You can derive the tip by subtracting amount_authorized from amount.

amount_authorized is the original authorized amount exclusive of the tip.
amount_captured and amount are the same and both are inclusive of the tip.