April was a month of transformation, protection, and expansion.

We overhauled the checkout flow from the ground up, dramatically improving performance and squashing critical bugs that had been holding back the experience. At the same time, we shipped our largest batch of compliance and fraud tooling improvements in recent memory — moving from reactive, manual processes to proactive, automated ones. And we opened a new payout channel entirely, with crypto offramp capabilities now live for merchants.

Let’s take a closer look at what we shipped.

A rebuilt checkout experience, faster and more reliable

What we shipped

The checkout flow received its biggest overhaul in months. Card Forms V2 was rebuilt from the ground up with unified theming and automatic dark-mode contrast detection, resolving the critical bugs that had led to the previous version being rolled back.

Beyond the rebuild, we made substantial performance improvements:

• The checkout JavaScript bundle was reduced by 41% (from 6.2 MB to 3.7 MB) by replacing heavy blockchain SDK dependencies with lightweight validations
• Purchase limit checks for non-card payment methods help to dramatically reduce latency at the moment of purchase
• Visual polish across card brand icons, placeholder text contrast, and theme color application rounded out a comprehensive improvement to the payment experience

Why it matters

Checkout is the highest-leverage surface in the product.

Every millisecond of latency and every rendering bug has a direct, measurable impact on conversion rates and merchant revenue. A 41% reduction in bundle size is much more than just a technical win. It enables faster load times for every customer, on every device.

By rebuilding the card form on a stable foundation and moving limit checks to in-memory counters, we've removed two of the most common sources of checkout friction.

Impact

These improvements directly protect merchant conversion rates and create a more reliable foundation for future checkout development.

Fraud prevention and compliance: from reactive to systematic

What we shipped

April brought the largest batch of compliance tooling improvements in recent memory. The changes span detection, verification, enforcement, and merchant control.

Key improvements include:

• Velocity limits system redesigned: Purpose-built admin dashboard with grouped views, audit logs, and data export
• Bank account name matching via Plaid Identity: withdrawals now verify that account holders match KYC-verified identities, closing a significant gap in the withdrawal verification process
• Geo-blocking reworked: merchants can now set independent rules for checkout and withdrawals, with enforcement options at the country, IP, and address level
• Visa Fraud Monitoring Program (VAMP) integration: enables proactive detection of merchants approaching fraud thresholds before they become a problem
• Flexible fraud protection model: merchants now choose between full chargeback insurance, decisions-only scoring, or no fraud protection, opening a new pricing tier

We also added configurable notification recipients for chargeback alerts and fraud reports, and velocity hold email notifications so merchants know when transactions are held and when funds are released.

Why it matters

Compliance infrastructure that relies on ad hoc database queries and manual intervention doesn't scale and misses risks too late.

These changes shift compliance operations from reactive to systematic. Purpose-built dashboards give compliance teams the visibility they need. Automated screening via Plaid and Visa integration catches risk earlier in the transaction lifecycle. And giving merchants control over their fraud protection tier means the system works for businesses at every stage.

Impact

These upgrades strengthen the platform's compliance posture while reducing the manual overhead that slows teams down.

Crypto offramp goes live

What we shipped

Coinflow's crypto payout capabilities expanded significantly with the launch of our Glide integration. Merchants can now generate static deposit addresses for crypto-to-fiat withdrawals — a simpler integration path that doesn't require per-transaction session setup.

Key features of the new offramp capability:

• Static deposit addresses via new API endpoints
• Support for both open-ended and fixed-amount deposits
• Webhook notifications when funds arrive
• KYT (Know Your Transaction) screening on all incoming crypto funds, ensuring they're screened against sanctions and risk lists before conversion to fiat

Why it matters

Crypto payouts have become a growing merchant need, but the complexity of existing solutions' integrations has been a barrier to adoption.

By supporting static deposit addresses, we've dramatically simplified the integration path. Merchants don't need to orchestrate a session for each transaction — they generate an address once, and it's ready to receive funds. KYT screening from day one means crypto offramp launches with the compliance rigor the product requires.

Impact

Crypto offramp expands Coinflow's payout coverage into a channel that's increasingly important for the merchants we serve.

Payments and payouts expansion

What we shipped

The payment infrastructure expanded on several fronts this month:

• Canadian EFT settlements: Canadian merchants now receive automated daily settlements in CAD, eliminating manual processing
• ACH transaction limits raised: From $2M to $5M per transaction, with IBAN per-customer limits also increased
• First-party payout settings: Merchant self-withdrawal configurations are now separate from end-user payouts, enabling different pricing and routing for each
• Per-merchant card network controls: Merchants can enable or disable specific card networks (Visa, Mastercard, Amex, Discover) directly from the dashboard
• Smart payment routing: IP-based geolocation and volume cap heuristics now enable automatic processor failover when capacity limits approach

Why it matters

Payment infrastructure needs to keep pace with merchant scale.

Higher ACH limits mean fewer workarounds for large transactions. Automated CAD settlements eliminate a manual process that adds latency and overhead for Canadian merchants. And separating first-party payout configs from end-user payouts gives us the flexibility to price and route each appropriately without forcing one model onto both.

Impact

These changes extend Coinflow's capabilities in geographies and use cases where we're seeing the most growth.

Platform modernization

What we shipped

We completed a significant frontend infrastructure upgrade this month:

• All core applications upgraded to React 19
• Merchant dashboard migrated from Tailwind CSS v3 to v4
• New Pylon support automations reduced manual steps in common support operations
• Admin tooling improvements: invoice payment from wallet, merchant-to-merchant transfers, and waiting queue job management

Why it matters

Infrastructure upgrades help to unlock features.

Staying current on React and Tailwind means access to performance improvements, better developer tooling, and compatibility with newer libraries. The support automations and admin tool improvements reduce internal overhead so teams can move faster on the things that matter to merchants.

Impact

These upgrades pay dividends across every surface of the product going forward.

Looking ahead

April was about overhauling the merchant experience, protecting what they've built, and expanding what's possible.

We rebuilt checkout from the ground up, shipped our most comprehensive compliance upgrade yet, launched a new payout channel, and closed a set of high-impact bugs and a security vulnerability. At the same time, we modernized the platform's core infrastructure to support what comes next.

As we move forward, the focus remains clear:

Make the checkout experience faster and more reliable. Strengthen compliance and fraud infrastructure. Expand payout coverage and geographic reach.

Because the best payments infrastructure is the kind merchants never have to think about.