Stripe
Money model
Section titled “Money model”4u Check uses Stripe Connect with separate charges and transfers:
- The guest pays the platform on Stripe Checkout, on behalf of the restaurant’s connected account. The restaurant is the merchant of record.
- A signed Stripe webhook wakes 4u Check, which reads the Checkout Session again and records the payment only from what Stripe reports.
- The payment is recorded on the POS check.
- Once the table is paid in full, its fee is split across its payments.
- 4u Check transfers each payment’s amount minus its fee share to the restaurant’s connected account.
This model lets the fee be decided after the payment and differ from payment to payment, which a fixed application fee at checkout cannot do.
What is built
Section titled “What is built”| Part | Detail |
|---|---|
| Hosted checkout | A Checkout Session per payment attempt, card, Apple Pay and Google Pay, the restaurant’s connected account as merchant of record |
| Idempotency | Every Stripe call is saved before it is made and sent with a stable key, so a retry after a crash replays Stripe’s answer |
| Webhooks | Signature checked over the exact body with a timestamp tolerance. A webhook only wakes a status read; it carries no money state on its own |
| Cancel | An unfinished Checkout Session is expired |
| Refunds | Partial and full, several per payment, each with its own key |
| Transfers | Planned and saved before sending, one per payment, deduplicated by transfer group |
| Refunds after transfer | The refunded part of the transfer is reversed |
| Fee carry-over | If a payment cannot cover its fee share after a refund, the rest is taken from the restaurant’s next transfer |
| Payouts report | Each payment’s fee, transfer and reversal for managers. See reports |
Configuration
Section titled “Configuration”| Setting | Meaning |
|---|---|
| Payment mode | stripe_test turns on the Stripe adapter |
| Secret key | A Stripe test secret or restricted key (sk_test_ or rk_test_). Live keys are refused |
| Webhook secret | The signing secret of the webhook endpoint |
| Return address | Where Stripe Checkout sends the guest back, with the payment attempt in it |
Keys are set on the server only, never in a browser or the repository.
Not built yet
Section titled “Not built yet”- Onboarding a restaurant’s connected account from the admin console.
- Dispute events from Stripe.

