Custom screens and support

When the drop-in UI does not fit, there is a headless variant. Plus staging guidance and contacts.

Building your own payment screens

The drop-in UI covers the large majority of POS integrations, and we recommend starting here. If your product has a design system the Blinc screens cannot fit, or you are embedding the payment flow inside an existing screen, there is a headless variant (blinc-pos-sdk-core) that exposes the same payment engine as an observable state machine with no UI at all.

It is a larger integration: you build and maintain a screen for every payment state, including attestation. Get in touch at [email protected] and we will send you the headless integration guide.

Support

For integration issues or to receive your paymentFacilitatorID:


Did this page help you?