Kinguin Merchant Verification: Prepare for Document Requests
Handle merchant verification with consistent records, secure submission and a clear case history.
Use Kinguin's current verification instructions for the document list applicable to your business. KeyMerchantHub does not certify merchant approval or promise a processing time. A clear, internally consistent submission gives the reviewer information they can assess.
Map the people and entity
Record which entity operates the merchant activity, who can represent it and whose details will be used for settlement. If the business has several owners or an authorized representative, answer the specific ownership or authority questions presented in the application.
Collect only what the process requests. Identity and company files belong in the official secure submission flow, not in a public support thread. Keep access limited and record when the files were submitted without duplicating them across many devices.
Read requests literally
A request for an entity document is different from a request concerning an individual representative. Check the requested name, document date, issuer and completeness. If the document you have does not match the requested type, ask for clarification before sending multiple alternatives.
When resubmitting, explain what changed. For example, an updated address document should be accompanied by a brief note identifying the previous inconsistency. That is more useful than an unrelated attachment with no case reference.
Merchant access and product approval
Approval of business information does not make every inventory item acceptable. Keep a separate sourcing and product-compliance file. The merchant who is responsible for a customer issue needs to trace the sold key back to the relevant batch and invoice.
If considering an existing merchant account, request written confirmation of the permitted ownership or operator change. Confirm whether new verification, payout changes or integration permissions are required. Never assume a historical verified status applies unchanged to a new entity.
Follow-up without conflicting applications
Use the existing case reference and state which request you are following up. Check whether the application is waiting on your response before asking for an escalation. Avoid guaranteeing a sales launch until current merchant access is confirmed.
See how to apply as a Kinguin merchant, daily merchant operations, and the Kinguin account specifications.
Verification source
Kinguin support includes verification and merchant resources. Account-specific requests in the official process take priority over general preparation guidance.
Sources and scope
Public sources reviewed on 3 October 2026. Operational checklists and hypothetical examples are KeyMerchantHub planning guidance. Confirm account-specific requirements and current commercial terms with the marketplace.
Related guides
How Does Kinguin Work for Merchants?
Understand catalog offers, delivery evidence and the role of a Kinguin merchant account in daily operations.
Read guide ↗How to Become a Kinguin Merchant: Application Checklist
Prepare your business and inventory information for the official Kinguin merchant application route.
Read guide ↗Kinguin Merchant API: Offers, Delivery and Safe Automation
Plan API authorization, product mapping and fulfillment evidence using the Kinguin developer portal.
Read guide ↗Kinguin Merchant Fees and Payments: Reconcile the Full Cost
Evaluate merchant economics using written fee terms, transaction records and settlement evidence.
Read guide ↗