Soca security
Security
without custody.
Soca protects the account, transaction, and integration without becoming the holder of the money.
Payment intent
$99.00
The model
Soca can coordinate money.
It cannot own it.
Funds remain in wallets controlled by their owners. Soca provides the software around the transaction, never a pooled balance or withdrawal gate.
Custody boundary
Control stays
with the owner.
Every Soca wallet has an exportable private key. The owner approves payments, sensitive changes require fresh confirmation, and settlement is recorded on Solana.
Read the non-custodial modelYou
Control the keys
Approve payments and export your wallet.
Soca
Coordinates
Builds the transaction but cannot sign for you.
Solana
Records settlement
Holds the public balance and transaction history.
Sensitive action
Fresh confirmation required
Confirm it is you
Face ID, fingerprint, or device PIN
Account protection
Sensitive actions
require you.
Passkeys use the security built into the customer's device. Payment approvals, wallet-key export, and settlement-wallet changes require confirmation rather than a reusable password.
See passkeys and account recoveryTransaction integrity
One intent.
One signed record.
The customer signs the exact payment. The fee split and merchant settlement are executed together, and the final transaction remains publicly verifiable.
Follow settlement step by stepIntent fixed
$99.00 · Northstar
Owner signed
5Lr9…bY7c
Fee split
1.5% recorded
Settled
Solana confirmed
Subscription safety
Permission with
hard limits.
A subscription is a bounded on-chain authorization, not a stored payment method that can be charged without limits.
Review the authorization safeguards04
The network enforces these limits. They are not optional merchant policy.
Developer security
Trust the signature,
not the request.
Every webhook carries a timestamped HMAC-SHA256 signature. Verify the raw request body and reject stale, modified, or forged events before fulfillment.
Implement webhook verificationtype invoice.paid
id event_01JY8K9
x-wc-signature t=1785250930,v1=7ad9…02fc
Environment isolation
Test stays test.
Live stays live.
API keys are scoped to one merchant and one mode. Test resources cannot reach live data, and mismatched requests are rejected.
Understand API-key isolationPrivacy boundaries
Clear about
what Soca can see.
Payment activity powers receipts and merchant operations. Private keys and customer signing authority remain outside Soca's reach.
Review every custody boundaryEvidence
Proof before
badges.
These claims link to the current product model and implementation guidance. Soca does not claim audits, certifications, insurance, or a formal bug bounty that it cannot publicly substantiate.
Secure by design
Your money.
Your approval.
Use Soca directly or build on infrastructure designed around explicit control.