01 · zero permission
Install the SDK and pass an amount plus receiving addresses. No dashboard setup, client secret, HMAC, or contract is required.
◆ stablecoin payments · permissionless by default
Your address is the account. SoulPass supplies the checkout, passkey wallet, multichain routing, gas sponsorship, and on-chain verification—without standing between you and your net settlement.
01 · zero permission
Install the SDK and pass an amount plus receiving addresses. No dashboard setup, client secret, HMAC, or contract is required.
02 · one payer action
SoulPass finds where the user can cover the checkout price, then atomically splits the included protocol fee with one passkey approval.
03 · chain-verified result
The promise resolves only after the backend verifies both merchant and protocol-fee transfers on the exact chain.
One package, two surfaces. Web3 products keep full control of transaction construction; Web2 checkouts pass an amount and receiving addresses to a single call. React bindings and a Solana wallet-adapter ship in the same package.
◆ install
npm install @soulpass/passkey-sdk◆ permissionless quickstart
import { createSoulPassPayments } from '@soulpass/passkey-sdk/payments'
const soulpass = createSoulPassPayments()
payButton.onclick = async () => {
const { intent, transactionId } = await soulpass.pay({
amount: '10.00',
currency: 'USDC',
recipients: {
solana: 'YOUR_SOLANA_ADDRESS',
evm: 'YOUR_EVM_ADDRESS',
},
// Opaque correlation only — SoulPass never reads your order schema.
reference: order.id,
// Fulfil on this signed webhook, not in the browser: a payer who closes
// the tab after signing has still moved the funds.
webhookUrl: 'https://api.yourshop.com/soulpass/webhook',
})
// Browser-side signal only — resolves after SoulPass verifies both transfers
// on-chain. Update the UI here; ship the goods when the webhook lands.
showReceipt(intent, transactionId)
}◆ optional developer wallet
Registration is not required to integrate. Create a SoulPass wallet only if you want a secure receiving address and one identity for future verified branding, webhooks, analytics, and fee benefits.
★ create or connect developer wallet◆ security boundary
A permissionless checkout is marked unverified in the payer’s wallet and shows both full destination addresses and the total before signing. The server snapshots every settlement option and rejects any completion unless both transfers match their exact on-chain proof. Optional verified developer profiles will add identity and operations features; they will never become permission to receive funds.