Generate and commit initial database migration

[therealjhay]

Description: The prisma/migrations/ directory is empty. There's no migration history, making it impossible to track schema changes or deploy to environments with existing data.

Requirements:

• Run prisma migrate dev --name init to generate the initial migration
• Commit the migration SQL file(s)
• Verify the migration applies cleanly to a fresh database
• Add migration documentation to README

Suggested execution steps:

1. Ensure DATABASE_URL is set to a development database
2. Run npx prisma migrate dev --name init
3. Review the generated SQL
4. Commit prisma/migrations/ directory
5. Test on a fresh database: npx prisma migrate deploy

Example commit message:

chore: generate and commit initial Prisma migration

Added init migration for Merchant, Payment, and Settlement models
with PaymentStatus and SettlementStatus enums.

[Emelie-Dev]

@Emelie-Dev has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I would love to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Emelie-Dev to this issue.

[Praxhant97]

@Praxhant97 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Greetings, i would like to work on your BettaPay-Backend project! Leaving the prisma/migrations/ directory completely empty blocks programmatic schema tracking, forces downstream developers to rely on destructive db push commands, and breaks clean automated CD pipelines targeting environments with pre-existing data; I am highly comfortable with TypeScript, Prisma ORM schema modeling, generating incremental SQL migration layers, and verifying deployment isolation boundaries on containerized test databases, which will allow me to seamlessly execute the init development migration cycle, review the structural integrity of the generated SQL tables for the Merchant, Payment, and Settlement models, and document the baseline migration execution lifecycle within your project README within a 12-hour timeframe.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Praxhant97 to this issue.

[mallison031]

@mallison031 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would like to

ℹ️ Repo Maintainers: To accept this application, review their application or assign @mallison031 to this issue.

[drips-wave]

Congratulations, @Praxhant97! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Praxhant97: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊