All information regarding payments within the Guest solution.


Every payment accepted within the Guest solution is associated to an Order. This can be thought of as a container or 'cart' for all products, tangible and physical, that are part a single purchase.

We do not support multiple payment types for a single order. Only a single credit card may be used for the entirety of the order.


Stripe is a 3rd party API that allows the Guest solution to tokenize, and process consumer credit cards.

Test Data

All uses of the SDK or API with a Sandbox API Key, will be creating dummy transactions, that will not actually be processed by a bank. Stripe makes a very clear distinction between dummy/test charges and actual production charges. This allows developers to test end to end cases, without incurring actual costs on a real credit card.

No real credit card numbers will work within the Sandbox. For a complete list of demo cards see here.

Captured Transactions

Stripe allows for the pre-authorization of a purchase, which will guarantee the funds on the payment card for up to seven days. This will happen in the solution while a booking is being confirmed by the supplier. See the Stripe documentation for more details.

Payment Strategies

The Guest app employs two different booking strategies, Buyable and Bookable.

Bookable Content

Bookable content requires confirmation from the selling party that the booking was indeed accepted and authorized. There also exists some supplementary information as part of the checkout flow that is required by the party offering the bookable content (e.g. Name of ticket holder, dietary restrictions etc.) These questions are defined by the supplier, and surfaced through the SDK.

Buyable Content

This strategy is not currently implemented

Buyable content refers to content that needs no confirmation.

Last updated