Last month, Coinflow gave merchants and platforms more flexibility in how they accept payments and onboard.

Card payments now route across processors by card type, and platforms can pre-fill sub-merchant onboarding through the API. New pay-in rails and Kenya checkout support widen who merchants can serve, and a few dashboard updates make account activity easier to see. Here’s what shipped in September.

Smarter card routing

What we shipped

• Card routing by BIN: card payments now route across processors based on the card's bank identification number (BIN)
• Stored cards across processors: one saved card token can now work with multiple tokenization providers

Why it matters

Routing by card type gives payments more options across processors, and saved cards no longer depend on a single tokenization provider. Together, these changes give merchants more flexibility in how card payments are processed and stored.

Impact

Faster onboarding for platforms and their sub-merchants

What we shipped

• Pre-filled sub-merchant onboarding: independent software vendors (ISVs) and other platforms can now send sub-merchant details to Coinflow through the API, so onboarding forms arrive pre-filled
• Review and acknowledge: sub-merchants confirm the pre-filled details and move forward instead of entering the same information a second time

Why it matters

Sub-merchants previously completed onboarding on the platform's website, then filled out the same details again in the Coinflow dashboard. Sending those details through the API removes the repeated step. For platforms, onboarding is often a sub-merchant's first experience of their payments setup, and confirming details the platform already has is a smoother start than beginning again. For merchants building a platform on Coinflow, this means less friction when bringing their own merchants on board.

Impact

More ways to accept payments

What we shipped

• New pay-in rails: merchants can now accept payments over Bitcoin Lightning and on-chain, with payments and refunds handled through one interface
• Kenya checkout support: customers in Kenya can now pay at checkout

Why it matters

More rails give merchants more ways to accept payments from more customers. Together, these changes give merchants more flexibility in how payments are accepted, processed, and stored. 

Impact

Clearer visibility in the dashboard

What we shipped

• Settings change history: merchants can review a log of changes to their settings and receive webhooks when those settings change
• Refund fee preview: refund fees now appear before a refund is processed
• Clearer name-match declines: declines for name mismatches now carry a dedicated code, with analytics and a detail panel

Why it matters

Merchants can see what changed in their account, what a refund will cost, and why a name-match decline happened. Together, these updates put more of the answers merchants need directly in the dashboard.

Impact

Looking ahead

September was about adding new ways to accept payments and giving merchants a clearer view of what happens next.

Card payments have more routing options, merchant onboarding has been streamlined, crypto pay-ins and refunds now share one interface, and the dashboard answers more of the questions merchants ask about their accounts. Each change makes it easier for merchants to accept payments the way their customers want to pay, and to understand what happened afterward.

Priorities heading into next month:

Keep widening payment options where merchants are asking for them. Keep making payment, refund, and decline activity easier to see and explain. Keep building flexibility into how payments are routed and stored.