Swipelux

Two-Sided Marketplace Escrow-Like Flows

Implement proof-of-funds verification for marketplace transactions without building custom custody infrastructure

Summary

Collect buyer funds into buyer's custodial wallet via checkout. Treat transfer.completed + REST verify as the signal to release goods/services. No custom custody or fund movement required on your side.

Problem → Solution mapping

PainCapabilityMechanism
Need "proof of funds"Server-led transferCreate transfer, verify completion
Hold until eventApp gatingRelease after verified completion
ComplianceKYC handledCustomer creation with documents

Architecture

Implementation steps

Create customer and transfer

curl https://wallet.swipelux.com/v1/transfers/tr_nEZHWur1pBSAKY7NlV \
  --header 'X-API-Key: sk_test_1234567890abcdef'

Show buyer balance (optional)

curl https://wallet.swipelux.com/v1/customers/cus_cK69MttD5nAUAbud1B/balances \
  --header 'X-API-Key: sk_test_1234567890abcdef'

Webhooks

Validate X-Webhook-Signature (HMAC-SHA256); re-fetch transfer before fulfillment.

UX choices

Use embedded widget for minimal drop-off; hosted link for email flows.

KPIs

% orders with verified funds; release latency.

Limits & caveats

USD→USDC only. This pattern gates delivery based on verified funds, not escrow re-allocation.

Troubleshooting

If webhook missed, poll by transfer IDs queued at order creation.

On this page