Start with accurate business information and a clear website. Share sensitive verification documents only through the secure channel your onboarding team specifies.
1. Write a business profile that answers the basics
Prepare a short explanation of what you sell, who buys it and where you operate. Include the company’s registration country, your customer markets, typical order value and expected monthly card volume. Distinguish current processing volume from a growth forecast. A new business should identify itself as pre-launch rather than present projected sales as processing history.
Describe subscriptions, free trials, advance orders and recurring billing clearly. If your catalogue includes more than one product type, explain the mix. A merchant review is more useful when the team can connect the products on your website to the business model in your enquiry.
2. Review your website before you send it
Look at the site as a first-time customer. Can someone understand the product, total price, delivery expectations and how to contact support? Review your refund, cancellation and subscription information for consistency with what happens at checkout.
Make sure the website you submit is the actual site you intend to process payments through. If it is not live yet, say so and explain what the reviewer can inspect. Avoid changing the substance of the business to fit an assumed approval criterion; an accurate explanation is the stronger starting point.
- Use clear product descriptions and visible pricing.
- Explain shipping or fulfilment timing before checkout.
- Make customer support and cancellation instructions easy to find.
- Check that company details and policy pages are consistent.
3. Put your processing history in context
If you already process payments, prepare an overview of your provider, monthly volumes, average order value and recent refunds or disputes. Explain unusual spikes or changes in the business rather than relying on a single headline number. If an account was restricted or closed, describe what happened and what has changed.
A processor may request supporting statements during detailed onboarding. Do not upload statements, identification or customer records into a general enquiry box. The initial message should give enough context to start a discussion; document collection belongs in an appropriate secure workflow.
4. Ask who is responsible for payment security
Before choosing an integration, ask the provider to explain which party handles card data and which responsibilities stay with your business. PCI SSC publishes PCI DSS as the standard covering protection of payment account data. Your acquirer or payment brand determines the applicable validation requirements.
A hosted checkout can change your technical responsibilities, but the words “hosted” or “secure” are not a substitute for understanding your setup. Ask for the relevant integration guidance and confirm the obligations that apply to your business.
5. Bring the questions that matter to your operations
Approval is only one part of choosing a payment arrangement. You also need to understand how it will work when sales, refunds and support requests arrive. Use the review conversation to ask for the proposed commercial and operational terms.
- Which products and customer countries can the provider support?
- What fees, reserves and other deductions would apply?
- What settlement schedule is proposed, and what can delay it?
- How are disputes, refunds and integration issues handled?
- What documents are required for the next stage, and where should they be sent?
Start small, then move to detailed onboarding
Crown Gate’s initial enquiry asks for your business website, category, country, volume and contact details. That creates a starting point for an introduction to the KingsGate team where suitable. It is not an approval decision, and no documents or payment commitment are required at this stage.
Your provider may request further information after the initial discussion. A clear, consistent first enquiry helps that conversation begin with the right context.
Further reading
PCI Security Standards Council: PCI DSSThis guide is general information for preparing a provider discussion. Individual requirements and terms are confirmed by the relevant provider.