Know what you’re authorizing.

Permara’s design separates identity checks, permissions, payment terms, and execution. The demo shows those decisions without moving real money.

Recipient checks

See who the payment is for and which destination checks are required. A completed identity check does not, on its own, authorize a payment.

See a recipient review

Payment limits

Review the amount, fees, permitted destinations, and timing before authorization. A proposed alternative must meet the applicable limits.

See a payment stopped at its limits

Changes and approvals

Material changes require the review and approvals defined for the updated terms. Earlier versions remain part of the record.

See a changed request reviewed

Clear payment states

Authorization, submission, and delivery are shown separately. An uncertain transaction result must be checked before another payment is attempted.

See the payment states

Information sharing

Review the requested information and recipient before sharing. A credential presentation may include necessary issuer, subject, timing, and cryptographic metadata in addition to the selected claims.

See a disclosure review · Arrives with the disclosure review

Demo status

The screens use sample data and simulated outcomes. Production security, provider arrangements, certifications, and service availability require separate verification before launch.

See the demo banner

Who Permara is

The entityPermara is not a bank or custodian

What it doesVerifies parties, prepares actions, enforces the rules you sign

Custody boundaryThe demo does not hold funds. Production custody, provider, and availability arrangements require separate verification before launch

Acting organizationEvery action is attributable to a person acting for a named organization

Where money sitsYour account → protected on-chain hold (both parties visible) → the recipient’s verified destination

Certifications and status

Stated plainly. Nothing below claims “aligned” or “compliant” without a scope.

SOC 2 Type IIPlannedPlatform controlsReport published when issued

Money transmission licensingNot yet — the demo moves no real moneyUS, state by stateLicense numbers published when granted

Card issuingPartner-provided · in progressAgent virtual cardsPartner named at launch

Identity verification (KYC/KYB)Partner-provided · sandbox livePerson + business checksProvider named at launch

Penetration testPlanned · pre-launchWeb app, APISummary letter on request

Subprocessors

HostingRuns the platformUS

Identity verificationKYC/KYB checksUS

Card issuingAgent virtual cardsUS

Payout providersFiat railsUS · EU

Email deliveryCodes and receiptsUS

Error trackingCrash reports, no financial dataUS

Provider names publish at launch — none are invented here.

Security architecture

EncryptionIn transit and at rest, everywhere

Access controlGrants in plain words; every action attributable

Key custodyIntended design: multisig with bounded session keys · production arrangements require verification before launch

LoggingAppend-only; overrides carry an audited reason

Incident responseStatus page opens with launch; incidents stated plainly

Secure developmentSigned requests, structural idempotency, secrets shown once then removed

Trust endures. Value moves.

When both sides agree, the money moves. Not before.