المسافر
Active member
- Joined
- Dec 3, 2025
- Messages
- 189
- Reaction score
- 0
- Points
- 16
Merchant Account Approval in Türkiye: Documents, Checks and Follow-Up
Build a consistent application file and track the provider’s decision
Build a consistent application file and track the provider’s decision
A merchant-account application to a payment provider in Türkiye is a verification file covering the entity, products, sales channel and bank account. Clear documents help the review but do not guarantee acceptance of every person or business. The information must match, and the reviewer must understand what you sell, how you deliver it and who manages the company. This guide organizes the file from the first eligibility inquiry to service activation, with a follow-up template that prevents conflicting documents being resubmitted. The final document list depends on the provider, service and entity type; use these examples to prepare, then follow the official request for your case.
The merchant file connects the sales activity, legal entity and bank account.
Start with the correct service and entity
Decide whether you need an in-store gateway, payment links, subscriptions, or a marketplace service involving other sellers. These solutions may have different eligibility and documentation requirements even within the same company. Do not treat approval for a simple service as permission to operate another model. Record the legal name, country, entity type and product categories before applying, then ask which service your application will be reviewed for.
If the company is foreign-owned or incorporated outside Türkiye, explicitly ask about the eligibility of the entity, authorized representative and account receiving funds. Do not infer the decision from another store owner's nationality. Individual or tax-exempt application options may exist within a particular scope, but do not generalize them to every business. The provider's decision is separate from business establishment, tax and licensing obligations that you must address for your circumstances.
Notice: A complete file or initial acceptance does not mean every product is activated or final approval is guaranteed.
Legal name and registration number
Create a basic information sheet containing the legal name exactly as documented, tax number, registration details, address and authorized representative. Use it to complete forms instead of copying old messages. The trading name customers see may differ from the company name, so explain their relationship. If you add a Latin-script or Arabic version of the name, retain the original accepted by the relevant organization.
Check recent changes in the company's address, name or management against updated documents. Do not attach a new document and an old one without explaining the timeline; the reviewer needs the current position. If the store operates under another party's brand, prepare evidence of the right to use it or the commercial relationship when requested. A consistent file shows that the entity selling is also the contracting entity and issuer of financial documents.
Prepare documents for the business type
PayTR pages explain that requirements vary by business type, citing examples such as tax documentation, signatures, identification and account details. Its terms distinguish companies and sole proprietorships for some documents. Obtain the list for your application through the provider's channel rather than treating a general internet list as definitive. Partner information, activity licenses or registration documents may also be required depending on your case.
Organize documents with clear names, dates and versions, and check scan quality before uploading. Required details, stamps and edges should be visible, and files must open correctly. Do not send expired documents or screenshots cutting off names. If translation, certification or a particular format is requested, ask for precise specifications rather than guessing what the reviewer accepts. Keep a submission record and avoid uploading files with identical names but different contents.
| Information type | Possible document example | Pre-upload check |
|---|---|---|
| Registration and tax | Registration document or tax certificate | Name, number and current status |
| Signature and representative | Signature circular or declaration, depending on the entity | Representative and authority |
| Identity and address | Documents officially required for the case | Validity, clarity and consistency |
| Bank account | Proof of account holder and IBAN | Correct entity and number |
Representative, owner and account permissions
Identify who can accept the contract, access the provider dashboard, issue refunds or change the bank account. The upload coordinator may not be an authorized signatory. If an accountant or employee applies, ensure the authorized person retains access to and approval of the application. When the provider requests ownership or beneficial-owner information, submit it accurately through the approved channel with the required documents.
Do not build the account around an employee's email without a transfer-of-access plan if they leave. Use a professional address that can be recovered and whose permissions can be managed, with secure login and a representative-update procedure. Keep contact details correct so additional-information requests and financial alerts reach you. Different application and follow-up email addresses may delay verification; cite the application number and use the approved channel instead of scattered correspondence without references.
Information verification comes before live payment processing.
Bank account and beneficiary matching
Check the account holder, IBAN, currency and country against service requirements. iyzico guidance refers to verifying the account receiving payments and matching its name with merchant details. Do not use a relative's or another company's account as a shortcut. If the provider allows a special arrangement, request written approval; asking about an exception is better than entering details that conflict with documents.
A single incorrect digit can disrupt transfers even when customer transactions succeed. Copy the number from an official document, then obtain a second independent check before submitting it. When changing the account after activation, confirm the provider's steps and effective date rather than assuming an immediate effect on a payout already in progress. Retain the change record and reference, and check the next transfer's beneficiary and amount.
Explain the products and fulfillment method
Risk assessment depends on what you sell and how you fulfill orders. Prepare product examples with prices, photos, descriptions and clear stock availability or lead times. For services, explain deliverables, how work begins and completion time. For preorders, disclose the expected period instead of presenting the product as immediately available. Many appealing names without a fulfillment explanation make the business harder to assess.
Provide the business documents requested, and do not argue for acceptance of restricted goods merely because another store sells them. For branded products, prepare supplier invoices or a legitimate basis for listing them if requested. Avoid adding radically different categories during review without updating the description. After approval, establish a procedure for notifying the provider of changes to the business, sales channel or delivery model under the contract; the file is not a step to forget after launch.
| What you sell | What to explain to the reviewer | Document or evidence on request |
|---|---|---|
| Stocked goods | Product, delivery and returns | Description and supplier invoices |
| Made-to-order product | Production and delivery time | Clear offer and terms |
| Digital service | Deliverables and performance evidence | Service model and appropriate policy |
| Licensed activity | Licensing authority and scope | Valid license in the entity's name |
Complete, consistent store pages
Make products, prices, contact details, seller information, delivery and return policies, privacy information and appropriate contractual information accessible to the reviewer. An unfinished store or broken button gives an incomplete picture. PayTR terms refer to these pages being active and to product-related documentation. If sales use social media or payment links, ask how to provide the required information for that channel.
Do not copy another store's policy and simply change its name; it may mention a carrier, period or entity unrelated to you. Check Arabic and Turkish versions, clarifying any controlling-language difference as appropriate for your store. Names, addresses and email should match documents, or the brand's relationship to the entity should be explained. Do not turn a policy into an impossible delivery promise. Accurate information supports verification, customers and the employee handling returns.
Check consistency before submitting
Have someone other than the form's preparer conduct a short review. Compare the name, number, address, representative, account and URL across all documents and pages. Record discrepancies as tasks to resolve; do not combine two different names into a new hybrid. If an old document correctly reflected an earlier period, explain the change date and provide evidence of the current position when requested.
Also check file format, size and clarity, and ensure links are not blocked by a login the reviewer lacks. If a temporary store password is needed for review, follow the provider's channel without sending full administrator credentials. Keep a final copy of the information submitted so later support answers remain consistent. This makes additional requests specific and lets you determine whether information is new or was already uploaded.
| Matching field | Where to compare | Action for a discrepancy |
|---|---|---|
| Legal name | Tax documents, contract, bank and website | Correction or documented explanation |
| Address | Form, document and page | Confirm the current position |
| Representative | Application, signature and identity | Confirm authority |
| Business activity | Product, description and license | Update the file before submission |
Following up with clear documents reduces delays and resubmissions.
Upload through a trusted channel
Start from the official website or approved dashboard and check upload links received through the established process. Identity and account documents are sensitive; do not send them to an unverified social account claiming to be a representative. If support needs another file, ask for the channel, document format and required information. Do not share a dashboard password or verification code with an external coordinator to complete the upload.
Save the application number, submission date, uploaded files and receipt confirmation. A successful upload does not prove document acceptance; its contents may fail review. Follow the status through the official process and set an internal review date without repeatedly messaging the reviewer every day. A provider's published assessment times are not a promise for every case; additional requests, business complexity and document accuracy can affect the process.

Follow-up template for applications and additional requests
Give each comment a row: what is required, who prepares it, its deadline, what was sent and the response. Ask one clear question if the request is unclear, such as “Is account proof in the company's name required in this format?” Sending many unnamed, unexplained files shifts the burden of interpretation back to the reviewer. Combine related updates in one reply carrying the application number instead of separate tickets for the same problem.
Hypothetical example: The file is sent on Monday; on Tuesday the reviewer requests clear bank-account evidence and an explanation of product fulfillment time. The coordinator records both tasks, corrects the bank document, adds a specific timing description and follows up on receipt. These are illustrative dates, not an announced service timeframe. The aim is to know the application's position and what is missing, rather than predicting an approval date outside your control.
| Hypothetical task | Owner | What was sent | Status |
|---|---|---|---|
| Account evidence | Finance | Document showing name and IBAN | Awaiting verification |
| Product fulfillment explanation | Operations | Description of timing and steps | Submitted |
| Seller-address consistency | Management | Corrected page and information | Closed |
| Service decision | Provider | File complete for review | Decision not guaranteed |

Initial acceptance, rejection and activation
On initial acceptance, read the offer, contract and included services before approving them. Confirm fees, settlement, reserves, refunds, cards and currencies; do not add unconfirmed features to the customer interface. Integration, testing and live activation may remain after signing, so ask for the current status and what permits actual payments. Use the correct environment keys and separate testing and live permissions.
If rejected, request the reason or clarification the provider permits and ask whether information can be corrected or a policy excludes the business. Do not rewrite the product description to pretend it is another activity. Correct the actual error, then follow the permitted reapplication process. Evaluating another provider against independent criteria may be appropriate. One company's rejection does not establish rejection by every institution, and a new application does not guarantee later acceptance.
Required outcome: A consistent file, a decision specific to the service and business, then a clear contract, test and activation process.

FAQs and file checklist
After activation, retain an organized package of entity details, contract, offer, verification history and application references, with access limited to responsible staff. Assign responsibility for updates when management, address, account or product categories change. Ignoring changes makes old documents a source of confusion during a future review, refund or pending payout, even if the original application passed without comments.
A good review confirms that the seller and document issuer are also the contracting party and transfer beneficiary. A green check in an upload form is insufficient. Before launch, have operations run a complete test order, finance read its report, and support explain its status to a customer. This turns approval from an administrative procedure into a service manageable every day.
Can I apply before completing the store?
Ask the provider about the service process, but prepare the information and pages required for review. A payment-link process may differ from a full store gateway.
Will an account in someone else's name be accepted?
Do not assume so. Provide the matching beneficiary account required by your service; any exception needs explicit provider approval.
Do complete documents guarantee acceptance of a foreign company owner?
No. Eligibility depends on the entity, representative, activity, service and provider policy; request an answer specific to your file.
Last edited by a moderator: