As-aAs-a

Professional service orders require clear scope, pricing, and delivery terms. As-a links conversations with orders so buyers and providers can review agreements and track progress.

The application uses Next.js and TypeScript, with Supabase for accounts, PostgreSQL data, file storage, and message subscriptions. Providers can create an order in a conversation; buyers can also order from a listing. The Tap checkout code checks payments on the server and handles repeated callbacks without settling an order twice. Database permissions and transactions govern who can read or change records.

The product demo includes a service directory, provider onboarding, conversations, order delivery confirmation, and administrator review. The repository includes local tests for permissions and payment logic. Live payment integration, migration of the existing database, and refund and dispute procedures still require acceptance before real transactions can be enabled.

The project reinforced the need to handle repeated payment callbacks, validate prices received from the browser, and define separate buyer and provider permissions for the same order. These rules belong on the server and in the database, with tests that check what each role can do.