Loading payments readiness
Payments
Payment underwriting turns on three things: how money moves through your business, how long after payment you deliver, and which markets you sell into. Get those wrong and an onboarding is accepted and then terminated.
Your business
The merchant
Sells, delivers, handles disputes.
The provider
Approves and settles
Owns the relationship, the decision and the terms.
ZKCAP
Advises on fit
Never a processor. Never holds merchant funds.
Business-model fit
Providers price and accept on model before anything else. These four patterns are treated very differently, and two of them touch a regulatory perimeter.
Customers pay you for goods or services you provide. This is a standard merchant relationship and the widest set of providers can consider it.
Recurring billing for your own product. Providers examine churn, refund behaviour and delivery continuity as well as the model itself.
Buyers pay through you and you pay sellers, contractors or suppliers. Funds pass through your business on the way to someone else.
Users hold a balance with you and can take it out. This is normally a licensed activity, not a merchant question.
Markets and currencies
Provider coverage depends on where your entity is incorporated, which markets you collect from, and which currencies you need to settle in. Treat it as a shortlist filter, not a detail to confirm later.
A provider that supports your model may not be able to onboard an entity from your jurisdiction. This is the first filter, and it is a hard one.
Where your customers pay from determines whether local acquiring, a local entity or a local method is required.
Needing more than one settlement currency narrows the provider set and changes the account structure you need behind it.
Paying suppliers, contractors or platform sellers is a separate capability from collecting, priced separately, and it is where perimeter questions surface.
No provider, method or market is presented as available until it has been confirmed against your entity and activity. A category being global does not make a service global.
Provider and integration dimensions
Beyond acceptance, these are the dimensions that decide whether a provider is workable for your team. Open one to see what sits inside it.
Integration work
Provider selection and onboarding preparation are in scope today. Whether ZKCAP also sells the implementation work itself is a commercial decision that has not been taken.
Risk and readiness
Payment underwriting looks at the live business, not only at the application. These are the areas that decide pricing and reserve terms as much as acceptance.
The gap between payment and delivery drives dispute exposure. Longer gaps normally attract a reserve, and reserve terms affect cash flow more than the headline rate does.
Published terms, refund policy and pricing are reviewed on your live site. Missing terms are among the most common onboarding rejections, and among the quickest to fix.
Processing history helps. A prior termination must be disclosed and explained — concealing it and having it discovered normally ends the onboarding.
Onboarding process
Two stages belong to the payment provider. The platform records what the provider reports and never anticipates a decision.
Structured questions establish which requirements you already meet and what is missing, before any application is prepared.
A qualified provider reviews the readiness output and scopes the work required.
The document pack is assembled against the requirement list, with information requests raised where evidence is missing.
The application is submitted to the payment provider and the submission evidence is recorded.
the payment provider reviews the application and may request further information. Each request is tracked as a first-class item.
The decision is recorded as issued — including a decline, which opens an alternate path rather than ending the engagement.
If the answer is no
Payment providers decline and sometimes terminate. What matters is whether the next step addresses the cause.
The provider declines the model
The shortlist is revisited against the specific reason. Where no provider in the set can support the model as it stands, that is stated rather than iterated on.
Approval comes with a reserve you cannot carry
The commercial position is reviewed with the provider, and alternatives with different exposure treatment are assessed before the account goes live.
A market or currency is unsupported
The fit mismatch is surfaced at readiness rather than discovered at go-live. Local acquiring or an additional entity may be the real answer.
The activity needs a licence
The licensing path is opened as its own workstream. A merchant onboarding is not a substitute for a permission.
Boundary
Stated once, plainly, so nothing on this page can be read as a promise the platform cannot keep.
Providers
Provider selection, onboarding preparation and integration planning are delivered by a verified provider whose verification state and credentials are shown on their profile.
Start
A structured set of questions establishes your model, markets and onboarding readiness, then produces a gap list. It is a preparation review, not an application, and it does not indicate that a provider will approve you.
Provider coverage depends on the entity's jurisdiction before it depends on anything else, so the review starts there.
Choose the jurisdiction of the entity to continue.
A readiness review is not an application.