Configure a MID once.
Reuse it everywhere.
Reusable configuration templates for MIDs and terminals. Apply a template to a new merchant and the right terminal mix, fee structure and routing rules are configured automatically.
Onboarding without re-configuring everything
Most new merchants in a given vertical need the same MID mix, the same fees and the same risk rules. Terminal Templates let you bundle that configuration once and apply it on every new merchant in the vertical.
Reusable templates
Define a terminal once and reuse it. A new MID starts from a configuration that is known to work instead of a blank form, which is where most setup mistakes are made.
Auto-applied
Different merchant tiers (Starter, Growth, Enterprise) can have different templates. Apply the right template based on the merchant's tier or volume commitment.
Per-vertical
The onboarding rules engine assigns the right template to each new merchant based on its application data. No manual setup per merchant.
Inheritable overrides
Templates can be overridden per merchant when commercials require it - the override sits on top of the template, with full audit log.
Versioned templates
When you update a template, existing merchants stay on their current configuration unless you migrate them. New merchants get the latest version.
How templates work
- Build
Define the template once - MID mix, fees, risk rules, routing logic, KYC requirements.
- Apply
On merchant onboarding, the rules engine selects the right template based on the application data and applies it.
- Iterate
Update templates as your products evolve. Migrate existing merchants to new versions on your schedule.
Frequently asked questions
How many templates can I build?
As many as your operation needs. Templates are usually organised by vertical or by acquirer, so the shape of your portfolio decides the number rather than a platform limit.
Can templates inherit from each other?
Yes. Templates can inherit from a base template and override specific fields - useful for tier hierarchies.
How do I migrate a merchant to a new template version?
A merchant is moved by applying the newer template to their terminal, with overrides preserved where they were set deliberately, so a migration does not quietly undo a specific arrangement.
Can I see which template a merchant is on?
Yes. Every merchant carries the template name and version it was provisioned with, plus any overrides applied.
Can templates be A/B tested?
Yes. Apply different templates to different merchant cohorts and measure approval ratios, settlement velocity and chargeback rates.
Where is data hosted?
Hosting, retention and data residency are set per deployment rather than fixed, and each brand is served from its own domain. Tell our team what your regulator and your customers require and we will confirm the arrangement in writing.