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.
On-receipt vs. on-reader tipping
The table below outlines some differences between on-receipt tipping and on-reader tipping.
|Country||DE, FR, IE, NL, UK, US||US|
|Reader||BBPOS WisePOS E||Any|
|Integrations/SDKs||All SDKs (JS, iOS, Android), server-driven||All SDKs (JS, iOS, Android), server-driven|
|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
The table below summarizes the specific API behavior.
|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_tip appears as a field in the total_details object in the API response when processing a payment. The amount field is inclusive of the amount_tip.||Tips are not directly represented but can be derived from the Charge object. The amount in the |
Tips in the underlying
Tips are not directly represented in the Charge object.
After capture, the fields below all show the same value inclusive of the tip.