Service
High volume and load balancing
In one line
More than one MID, split on rules you control.
What it is
Every merchant account has a monthly volume cap. Growing past it triggers a review and, often, a hold — which arrives precisely when a business can least afford it. The structural answer is more than one account.
Multi-MID structures also address the failure mode that ends restricted-vertical businesses: a sponsor bank exits your category and your only account closes with 30 days' notice. Two banks means one exit is a routing change, not an outage.
Capabilities
What you get, specifically.
Rule-based distribution
Split by percentage, card brand, currency, ticket band, product line or descriptor. Rules change in the gateway, not in your code.
Cap-aware routing
Routing weights respond to each MID's remaining monthly headroom, so volume moves before a cap is breached rather than after.
Cross-bank redundancy
MIDs placed with different sponsor banks where the vertical allows it, which is the only redundancy that survives a category exit.
Consolidated reporting
One reporting surface across every MID, with per-MID ratio and volume broken out for the reviews that matter.
Specification
The detail.
- MIDs per merchant
- As underwriting supports
- Routing
- Percentage, attribute-based, cap-aware, failover
- Reporting
- Consolidated and per-MID
- Per-MID volume cap
- Set at underwriting
Rows reading set at underwriting are not omissions. Those figures are decided per merchant against your vertical, volume and history, and you will see all of them in writing before you sign.
Tell us what you sell.
Before anything sensitive changes hands, we will tell you whether a route exists for your vertical, roughly what shape it takes, and what underwriting will ask you for.