Compliance before execution
A transfer cannot proceed unless the required compliance decision and activated payment path exist.
Responsibility is built into the way PorteCash handles identity, payment decisions, financial records and exceptions.
Behind the simple interface is a design that separates payment intent from funding evidence, delivery and settlement.
A transfer cannot proceed unless the required compliance decision and activated payment path exist.
Identity data, live financial data and test financial data live in separate PostgreSQL databases.
An immutable double-entry ledger distinguishes available, reserved and pending balances.
Uncertain submissions pause for verification instead of being blindly resent.
Funding confirmation, compliance review, provider response, settlement and reconciliation should never be mistaken for the same thing. PorteCash keeps those events distinct.
Security controls and software tests are not a substitute for external financial authorisations, partner contracts or independent certifications. Real-money services remain inactive.
Find answers about product status, security and what to expect as services are activated.