Start with the transaction pattern
A request for FTD processing often begins with a monthly volume figure. That number is useful, but it leaves out the shape of the activity. Two merchants expecting the same total deposits can present very different customer geographies, transaction sizes, acquisition channels and support demands. A processing structure should be assessed against those details before the business compares approval messages or headline prices.
Part thirteen examined what happens after a first deposit is accepted. This article focuses on the brief that should shape the arrangement before volume arrives. It is an independent planning framework for lawful businesses. It does not promise that a particular country, business model or deposit flow will be accepted by FixPays, an acquirer or any other provider.
Explain why segmentation matters
Visa's public Acceptance Risk Standards describe underwriting policies tailored to business segments, including merchant activities, countries and origination channels. That supports a limited point: an acquiring review considers more than the merchant's total sales forecast. The applicable current standards and provider requirements should be confirmed for the actual arrangement, rather than inferred from a generic industry description.
Prepare a factual profile of the business activity and the entity conducting it. Identify the customer markets being proposed and the permissions relevant to serving them. Keep legal market access separate from technical payment coverage. A provider being able to receive a card transaction from a country does not establish that the merchant may lawfully solicit or serve the customer there.
Describe geography at the right level
Distinguish the merchant's location, customer residence, customer acquisition market and payment instrument geography. These may differ, and a single country field can hide the distinction. Explain which information is observed, which is declared and which is only a forecast. The provider needs to understand the actual pattern without being presented with an artificial certainty that the merchant cannot support.
For a hypothetical campaign aimed at one market but attracting customers from several others, record the difference and investigate the cause. Do not simply relabel the traffic to match the original application. Define who can stop the affected campaign and who reviews whether the new pattern is permitted. A credible operating brief includes a process for handling change, not just an idealised launch scenario.
Show the distribution of ticket sizes
An average deposit size can conceal a wide range of transactions. Provide a sensible distribution showing typical amounts, larger deposits and expected peaks, using historical evidence where available. For a pre-launch business, label estimates clearly and state the assumptions behind them. Avoid presenting an ambitious commercial target as verified processing history.
Explain how first deposits differ from later funding in the proposed model. The provider may need to understand the frequency of attempts, successful transactions and customer-level activity. Keep those measures separate. A forecast of deposits is not necessarily a forecast of payment attempts, and several attempts by one customer do not represent several newly acquired customers.
Connect acquisition to the payment journey
Describe how a customer reaches the deposit page and what they are told before paying. Include the principal acquisition channels, relevant offer types and the teams responsible for approving them. A provider cannot assess the complete customer proposition from a screenshot of the payment form alone. Preserve the relationship between the campaign and the transaction without collecting unnecessary personal information.
Map the steps between registration, required verification, payment initiation and account credit. Identify which system confirms each step and how failures are handled. Do not treat a successful authorisation as proof that the customer account should immediately receive unrestricted functionality. The relevant compliance, product and payment decisions may require separate controls and should remain distinguishable in the implementation.
Make the financial requirements explicit
Treasury should explain the settlement currencies, expected payout cadence, funding obligations and tolerance for restricted liquidity. These are requirements to discuss, not terms a provider has already accepted. Ask for a worked example of how a representative deposit appears in reporting and how proceeds become available under the proposed agreement. Compare cash-flow assumptions with the actual contract.
Include refunds, disputed transactions and customer withdrawals in the operating map where relevant. They are not interchangeable movements. Identify which party approves each action, which provider executes it and which ledger records the obligation. A structure that supports incoming deposits but leaves outgoing customer obligations unexplained is incomplete, even if the initial acceptance experience appears smooth.
Agree review points before scaling
A useful proposal should state the approved scope and what changes require further discussion. Examples for review can include new markets, materially different ticket sizes, acquisition changes or unexpected transaction behaviour. The actual triggers must be agreed with the provider and responsible specialists. They should not be invented as universal scheme thresholds or treated as permission to conceal changes below a chosen number.
Start with a controlled launch population where appropriate and compare observed activity with the brief. Document differences promptly. If the forecast proves inaccurate, revise the operating plan rather than forcing transactions into the original description. The review should include marketing, compliance, finance and payment operations so that one team's growth target does not silently change another team's risk assumptions.
Compare structures using the same facts
When evaluating providers, send the same accurate business brief and clearly identify any differences in proposed scope. Otherwise, two quotations may appear comparable while one assumes a different geography or funding pattern. Keep unknown terms visible. A lower price is not a complete comparison if settlement restrictions, reporting access or exception responsibilities remain unanswered.
Record the decision and its conditions in a form the implementation team can use. Include the approved entity, channels, transaction profile and operational contacts. Preserve later revisions with effective dates. The strongest structure is not necessarily the one described in the most enthusiastic sales message; it is the one whose permitted scope, financial behaviour and responsibilities match the business that will actually operate.
What it means to Merchants
Define FTD processing through the actual customer and transaction journey: geography, ticket distribution, acquisition source, verification steps and financial obligations. Give providers a consistent, evidence-based brief and confirm the scope in writing before scaling. A suitable structure supports accurate review and operational continuity, while merchant market permissions and acquiring-bank risk remain independent requirements that cannot be replaced by payment acceptance alone.