Availability and release prerequisites

Implemented

The existing Next.js, Fastify, PostgreSQL, Prisma and Better Auth foundation now includes PT/EN marketing pages, authentication screens, merchant dashboard, transaction detail and CSV export, scoped API keys, request history, signed webhook management, checkout builder, settings, session revocation and fixed receiving destinations by network and asset. Each account has one business, while the operator alone manages the global 4P credential. Sandbox sessions and simulated payments are persistent and explicitly marked.

External launch requirements

The official Magnum media kit is installed: the original SVG paths, application symbols, favicons and social images are preserved. Future identity updates must replace the supplied assets without recreating the logo.

Configure Resend or SMTP with a verified sender, the public support contact and the operator's legal identity. Registration remains off until the transport is configured and explicitly enabled. The Google button is available in the interface but OAuth requires its own configured client credentials. The legal pages describe current software behavior and do not claim approved financial terms.

The public origin is https://magnum.lat. Preserve its authorized VPS routing, certificate renewal, and existing MX/TXT records during deployment. A successful web release does not establish email delivery or financial readiness.

Financial activation

Live payments and customer-selected wallets remain blocked in code. A business can save its own fixed receiving destinations, but this does not approve settlement. The operator must confirm account-specific networks, beneficiary policy and explicit authorization of the global-credential platform model with 4P. Activation requires a reviewed implementation, reconciliation tests and a separately authorized bounded live test. No environment variable alone grants financial permissions.

Not implemented as product features

Billing, invitations, role administration, MFA enrollment, withdrawals and custody are not presented as available features. No balances or provider endpoints are invented.