Roots Review: Is Its Payment Network Ready to Use?

Roots’ website describes a payment network built around three offerings: Roots App, Roots Pay and CIMS. The app is presented as a card product, Roots Pay as NFC acceptance for merchants, and CIMS as an identity, routing and settlement layer for institutions. It says users can pay by tapping a phone or card, while merchants receive a confirmation and settlement to a bank account in local currency.

The site also describes human-readable payment identifiers, institution-configured counterparty rules and a finality window during which a transfer can be halted or reversed. These are product claims, not a substitute for published technical documentation or a live service commitment. The site speaks chiefly to neobanks, fintechs, acquirers and other institutions; it does not establish that a general consumer can sign up and use the app today.

There is an important identity mismatch: a DeFi listing describes Roots as a Berachain collateralized-debt-position protocol that accepts LP tokens and mints MEAD. That is materially different from the payment network described on Roots’ site. Confirm with Roots whether these are related products before relying on information about MEAD, Berachain or the payment service as if they describe one offering.

Roots does not publish a payment fee schedule, card charges, conversion rates or merchant pricing in the product description. The website claims same-day merchant settlement and says its payment flow converts stablecoins into local currency, but it does not say what that conversion costs or whether the claim applies in every market. “No FX spread” appears as a product claim for Roots Pay; ask how that is defined and whether other charges still apply.

Before using the service, request a written breakdown for your specific route: any app or card fee, merchant acceptance fee, stablecoin-to-fiat conversion charge, network transaction cost, payout fee and any minimums or limits. If you are a merchant, confirm whether settlement timing depends on your acquirer, bank, country or transaction type. If you are an institution, ask whether integration, access or ongoing service fees apply.

Do not estimate the cost from the MEAD listing or assume fees for the CDP apply to Roots Pay. The products and their relationship are unclear, and Roots has not published enough pricing detail to compare the payment service with other rails on total cost.

Roots says it is a financial technology company, not a bank or money transmitter, and describes its software protocol as non-custodial. It says banking, money transmission and fiat-to-digital-asset exchange are handled by regulated and licensed financial institution partners. Its disclaimer also says digital assets are not legal tender, are not government-backed and are not covered by FDIC or SIPC protections.

That tells you what Roots says about its model, but not which partner holds or moves funds in a specific payment, where the partner is licensed, or what protections apply to your account. Roots does not name those partners in the described content. The site also does not publish audit details for the payment network or explain an independent security review. A DeFi listing reports two audits, but the connection between that listing and this payment product is unclear, so do not treat that as proof that Roots Pay or CIMS has been audited.

Before sending money, ask for the partner’s legal name, the terms governing your funds, applicable jurisdictions and the process for complaints, errors and reversals. Do not rely on “non-custodial” alone: a payment can still involve a financial partner or conversion service with its own risks and terms.

Roots describes a tap-to-pay flow: a customer presents a phone or physical card to a merchant reader, the merchant receives an approval, and the payment is routed for settlement in local currency. The company says Roots Pay works alongside existing card schemes and supports standard merchant terminals. It also claims settlement can reach the merchant’s bank within one business day or the same day, depending on the wording used for the product.

For CIMS, Roots says identifiers resolve on-chain and institutions set their own counterparties, transaction limits and fraud-hold durations. It describes settlement finality in under a second, with a configurable window for cancellation or reversal. Those are performance and design claims; the website does not identify the chain used for the payment network, publish independent service metrics, or give a consumer-facing supported-country and device list.

The site invites prospective users to book a demo and directs visitors to check out the app, but does not explain public signup, supported wallets, card eligibility or account setup. If you are evaluating it, ask for a demonstration of the exact product, a supported-market list and the service-level commitments before planning around settlement speed or availability.

Roots is more clearly presented as infrastructure for businesses than as a self-serve crypto app. Its stated audience includes neobanks, fintechs, merchants, acquirers and institutions building payment products. The product pitch is an integrated app, NFC acceptance and settlement layer, with institution-specific compliance rules rather than a single operator imposing one policy.

The trade-off is that several decision-critical details are missing: payment fees, named partners, supported jurisdictions, consumer eligibility, technical documentation, service terms and the relationship between the payment network and the Berachain CDP listing. The website says compliance is configured by each institution, so users should not assume Roots itself applies the same KYC checks or protections to every service. Ask the specific provider what identity checks and transaction limits apply.

For now, treat Roots as a potential infrastructure provider to evaluate, not a proven replacement for your bank, merchant acquirer or wallet. If you need a product you can use immediately with clearly published costs, custody arrangements and support rules, choose a service that makes those details available before signup.