blindpaylabs/blindpay-skills

Overview

This skill integrates with BlindPay to manage stablecoin↔fiat flows, receiver KYC, bank accounts, blockchain wallets, virtual accounts, and offramp wallets. It provides the API patterns and workflows needed to create quotes, execute payins and payouts, and handle multi-chain, multi-currency routing. Use it to automate conversions, compliance checks, and payout delivery across global rails.

How this skill works

The skill calls BlindPay APIs using an API key (Authorization: Bearer) and an instance ID in the URL path. Typical flows: create/verify a receiver (KYC/TOS), attach a bank account or blockchain wallet, generate a time-limited quote, then execute the payin or payout. Webhooks surface real-time events and errors so you can reconcile status and trigger retries or refunds.

When to use it

• Convert inbound fiat to on-chain stablecoins for users (fiat → stablecoin payins).
• Convert user stablecoins to fiat and send to bank accounts (stablecoin → fiat payouts).
• Manage receiver onboarding, KYC/KYB, and TOS acceptance for compliant payouts.
• Create virtual US bank accounts for receivers who need dedicated ACH rails.
• Auto-convert incoming stablecoins via an offramp wallet to local fiat.
• Test integrations in development using simulated tokens and auto-approved KYC.

Best practices

• Always include the instance ID and Authorization header on every request.
• Create quotes immediately before execution; quotes expire in 5 minutes.
• Implement webhook handling for payout/payin status, rejections, and refunds.
• Use development instances and test tokens (USDB) for end-to-end testing.
• Treat BlindPay as non-custodial: handle on-chain approvals and monitor wallet balances.
• Map common API errors to actionable UI flows (accept TOS, retry with new quote, top up wallet).

Example use cases

• A marketplace pays sellers in local fiat by converting seller USDC into bank transfers via BlindPay payouts.
• A remittance app accepts fiat payment instructions, then issues USDC to recipient wallets after payin settlement.
• An issuer provisions virtual US bank accounts so receivers can receive ACH payouts without separate bank onboarding.
• A fintech automatically offrams received stablecoins to local currency and deposits to partner bank accounts.
• A test suite simulates failure and refund scenarios (use amounts like $666 or $777 and 'Fail' as first name).