Skip to main content
SimplePay isolates each merchant’s data authority. Merchants use the API and never receive direct PostgreSQL credentials.

Database provisioning eligibility

SimplePay provisions the dedicated data plane after the merchant passes payment readiness. A merchant with incomplete readiness receives no tenant Neon project. The decision verifies:
  • Active merchant and environment
  • Approved product application
  • Granted payment capability
  • Usable payments account
  • Complete card requirements
  • Available live tokenization when required

Dedicated resources

Each approved merchant receives an exclusive Neon project, compute endpoint, and PostgreSQL database. Another merchant never shares that project, restore timeline, or compute. The database separates products into schemas. Runtime roles use least privilege and never connect as owner.

Control plane metadata

The control plane stores routing, readiness, manifest versions, and secret references. It never returns connection strings, passwords, or physical IDs to the customer.
Search, content delivery network, and reporting copies are rebuildable projections. The merchant database remains authoritative.
Last modified on August 22, 2026