Accounts and payments

Egbe supplies integration contracts for customer accounts and Stripe payments. Your product still needs to connect those operations to its own users, sessions and access rules. Start from the existing product rather than adding another authentication or billing system alongside it.

Customer accounts

Choose the account-entry methods your customers need. The Product Auth instructions cover Google, email-link and email/password flows, secure sessions, protected pages and recovery of a customer’s progress through sign-in.

For Google sign-in, Egbe manages the Google OAuth client and verifies external identity. Your app creates or finds the local user, links that identity, establishes its own server-side session and enforces permissions. It also owns logout. The app does not need its own Google client secret. Follow the Google sign-in contract.

Verify the complete live journey: first signup, repeat login to the same account, return to the intended action, refresh, logout and denial of protected access. Email-link login additionally needs receipt and use of the actual message. A redirect or a rendered login form is insufficient evidence.

Payments and subscriptions

Through Egbe, your agent can integrate Stripe checkout for one-time purchases or subscriptions, discounts and promotion codes, and customer billing management. Use the payment instructions for the selected workflow and current API contract.

Keep one product-owned plan catalog consistent across pricing, checkout and access rules. Provider readback confirms Stripe objects; the product database owns the customer’s resulting entitlement state. A checkout return URL is navigation, not proof of payment. Grant paid access only after the signed event has been durably and idempotently applied.

Payment requests that create provider objects need their documented retry and idempotency handling. If an outcome is uncertain, reconcile it before creating another checkout or purchase. Your agent should test both the customer-facing handoff and the application’s resulting access behavior.

Keep secrets on the server

Deployed product code uses the separate runtime identity supplied by Egbe hosting. Do not copy the local agent’s project key into app code, browser variables or build output. Google identity exchange, checkout creation, webhook secrets and billing identifiers belong on the server.

The product’s revenue, payment processing and payouts are distinct from the Egbe Wallet used to operate the business. Consult access and costs and the current commercial terms before making fee or payout commitments.