Use case summary
Configure payment methods, routing rules, fees, currencies, balances, and access rights separately for each merchant, with changes to one leaving the others untouched. Merchants get their own portal for payments, payouts, and reports. Result: the portfolio grows without your operations team growing at the same rate.
- Founder & CEO
- Payment Ops
Why each new merchant adds permanent operational work
Every merchant you sign needs its own setup: which payment methods it gets, how its traffic is routed, what fees it pays, which currencies it settles in, and who on its side can see what.
Done by hand, that scales badly. The configuration lives in someone's head or a spreadsheet; a change made for one merchant can reach another by accident, and each new merchant brings a standing support load of status questions, payout questions, and report requests.
All of it lands on the same small team that is supposed to be signing the next ten merchants. A growing portfolio then shows up as growing operations headcount instead of margin.
How to run a merchant portfolio from one workspace
Each merchant gets its own configuration and environment, and your team works across all of them from one place.
- 1
Configure each merchant on its own terms
Set payment methods, routing rules, fees, currency conversion rules, processing limits, balance accounts, and rolling reserve settings per merchant. Adjusting one merchant's setup leaves the rest of the portfolio as it was.
- 2
Keep merchants isolated from each other
Each merchant has dedicated webhook endpoints and its own event stream. Customer records, stored payment methods, and transaction history stay inside the merchant where the payment happened, with no data crossing between accounts.
- 3
Set risk rules per merchant
Allow and deny lists, 3D Secure rules, and transaction blocking logic are defined for each merchant independently, so a stricter rule for one does not apply to the others.
- 4
Support whichever integration each merchant wants
Hosted checkout, embedded fields, direct API, or webhooks all apply the same methods, routing, and fees you configured for that merchant. Embedded fields let a merchant keep payment fields inside its own interface while reducing its PCI DSS scope.
- 5
Let merchants answer their own questions
The merchant portal gives each merchant access to its own payments, refunds, chargebacks, payout schedules, fee breakdowns, rolling reserve balances, and settlement details. You control what each one can see and do.
- 6
Watch the whole portfolio from one workspace
A single operations view covers payment activity, provider status, and issues across every merchant. Payment reviews open the timeline, provider responses, and failure reasons for any transaction under any merchant, and alerts fire when activity spikes, a provider becomes unstable, or webhooks start failing.
What you get
Adding a merchant means configuring an account, and the work of running it stays roughly the same size.
Operations that scale slower than the portfolio
Setup, monitoring, and reporting stay centralized as merchant numbers grow, so signing more merchants does not automatically mean hiring more people to service them.
Routine questions answered without your team
Merchants check their own transactions, payouts, reserve balances, and fee breakdowns in the portal, which leaves your operations team handling exceptions rather than status updates.
Changes that stay inside one merchant
Because configuration, risk rules, and webhooks are scoped per merchant, adjusting one merchant's routing or fees carries no risk to the accounts around it.
A back office you did not have to build
The merchant-facing portal runs under your brand, so you can serve merchants properly without putting engineering time into building and maintaining an interface for them.
A high-risk PSP was live on Corefy in 10 days
A high-risk payment service provider moved to Corefy under an urgent timeline, having outgrown a platform whose multitenancy and routing constraints no longer fit a growing merchant portfolio. Ten days covered the MVP deployment, rolling out the merchant portal, configuring the first routing and firewall schemes, and setting up analytics and reporting for reconciliation. Each of its merchants now has access to a separate commerce account where they monitor transactions, track balances, and export data without waiting for the PSP's support team.