Crypto Payment Rail Developer - WooCommerce Plugin (Card-In, USDC-Out on Polygon)

We're a high-risk payment processor serving merchants in peptides, supplements, and nutraceuticals — verticals declined by Stripe, Square, and PayPal. We are still searching for the right crypto rail solution and we want to hear from developers who have already built this flow before and can replicate it for us. --- ## What We're Trying to Solve - Customer pays with a credit/debit card at a normal WooCommerce checkout - Funds settle as USDC on Polygon to a wallet we control - The customer experience is a standard card checkout — no wallet creation, no crypto purchase, no seed phrases, zero crypto UX on the shopper side - Card-in, USDC-out - We pay out merchants from our master wallet --- ## The Two Hard Constraints ### No SSN collection on KYC Any solution that requires end customers to submit SSN, full government ID verification, or heavy KYC at checkout is a non-starter. The checkout needs to feel like a normal card transaction. ### No chargeback liability on us We cannot be the party liable for chargebacks. The rail provider (or the card acquirer behind them) must carry chargeback liability. We are not a card acquirer and will not sit in the chargeback chain. If your proposed architecture puts us on the hook, it's the wrong solution. --- ## Who We Want to Hear From Developers who have already built and deployed a card-to-crypto checkout flow — ideally for high-risk merchants — and can show us it working. We are not looking for someone to experiment on our dime. We want to replicate a pattern you've already solved. --- ## In Your Proposal, Answer These Directly 1. **Have you built this exact flow before?** Card-in, stablecoin-out, no crypto UX for the end customer, chargeback liability held by the rail. If yes, describe the project (even generally if NDA-covered), show screenshots, demo links, or repos. 2. **Which rail did you use and why?** We've looked at PayRam (ruled out — wrong UX), NOWPayments, Coinflow, BVNK, MoonPay Commerce, Zero Hash, Bridge (Stripe), Sheepy, Onramper, Guardarian, Alchemy Pay. Tell us what you'd build on and why — specifically addressing the no-SSN and no-chargeback-liability constraints. 3. **How does your proposed stack handle KYC and chargeback liability?** Who takes the card risk? What data does the customer submit at checkout? Does your rail sponsor the acquiring relationship? 4. **Can you show us it in production?** A live URL or video of a working card-to-USDC checkout you've built is worth more than any written proposal. 5. **Timeline and cost** to replicate this into our existing stack (see below) with one live test merchant. --- ## What's Already Built on Our Side - **Marketing site + merchant portal** (pay-vantage.com) — Next.js on Vercel - **Supabase backend** — Postgres, Merchant ID lookup edge function, transactions table - **WooCommerce plugin (v5)** — PHP, partially built, routes via Merchant ID lookup - **GitHub repo, LocalWP test environment** --- ## Required Experience - Proven, demonstrable card-to-crypto checkout build (required — we will ask for proof) - WooCommerce plugin development (PHP) - Next.js / Vercel - Polygon / EVM USDC settlement - Supabase or equivalent Postgres backend - High-risk merchant processing (strongly preferred) --- ## Not Looking For - Solutions where the customer creates a wallet or buys crypto themselves - Solutions requiring SSN or heavy KYC from the shopper - Solutions where we carry chargeback liability - Generic proposals from developers who haven't built this before --- ## Project Type Fixed-price MVP + ongoing retainer. --- ## To Apply Lead with what you've already built. If you haven't built a card-to-crypto flow before, please don't apply — we're specifically hiring someone who has solved this problem and can show us.