iDenfy

Crypto neobank infrastructure: 8 layers behind a crypto card A crypto card can spend from a self-custody wallet or from a balance funded in advance. Those products may look similar in an app, but they create different requirements for custody, payment authorisation and settlement. The infrastructure has to support how the neobank holds and moves customer funds. Some of the providers across the stack: 💳 Card issuing: @raincards, @wirexapp, @immersve, @Monavate_News, @reapglobal ⚙️ Card processing: @lithic, @HelloThredd, @Paymentology, @marqeta, @i2cinc, @SoFiTechSol, @highnotesocial, @E6_Technology 💸 Pay-ins and payouts: @BVNKFinance, @ConduitPay, @lightspark, @StableCoin, @ZeroHashX, @Transak, @yellowcard_app, @moonpay 🏦 Fiat accounts and rails: @OpenPayd, @BankingCircle, @ClearJunction, @niumglobal 📒 Balances and ledger: @formancehq, @ModernTreasury, with examples like @solana and @Plasma supporting onchain balances 🔐 Wallets and custody: @FireblocksHQ, @dfnsHQ, @BitGo, @privy_io 🛡️ Risk and compliance: @sumsub, @sardine, @withpersona, @Veriff, @iDenfy, @trmlabs What layer do you think is the most important in the neobank stack? Or, perhaps, only distribution matters nowadays? Follow @neobankster for more insights.