Bailee SDK Suite (local demo)

Merchant flow:

1. Web SDK (initBailee): merchant backend creates a session (sessionId only in the redirect).
2. Browser opens the pay service /checkout page (or baileeapp:///sdk-product directly if payBaseUrl is a custom scheme).
3. Mobile app loads product / line-item details for that sessionId (no web payment UI in the SDK).

Packages

• packages/web-sdk: initBailee — mount button, createSession, redirect / open app
• packages/pay-service: Express — session store + /checkout landing (deep link into app)
• packages/merchant-demo: sample merchant site + /api/bailee/create-session proxy

Build

From this directory:

npm install
npm run build

This compiles only @bailee/web-sdk (outputs packages/web-sdk/dist/). Other packages are no-op build scripts for workspaces.

• npm run build:all — runs build in every workspace (web-sdk + no-ops).

Run locally

Terminal 1:

npm run dev:pay

Terminal 2:

npm run dev:merchant

• Merchant demo: http://localhost:4100
• Pay service: http://localhost:4200

Required env (merchant → Bailee API)

For packages/merchant-demo to create sessions in the Bailee backend, configure its server (see packages/merchant-demo/src/server.mjs).

Notes

• Do not put sensitive cart data in the deep link — only sessionId.
• Default app deep link target is baileeapp:///sdk-product?sessionId=... (see pay-service APP_DEEP_LINK and mobile app/sdk-product.tsx).
• sessionId should be short-lived and unguessable.