SASAHUB — Payment Policy
Section 1. General Provisions
1.1. Purpose of the Policy
This Payment Policy establishes general rules for arranging and supporting payments connected with goods, works, services, digital products, subscriptions and other paid SASAHUB services. It defines the roles of Users, the Operator and integrated payment providers and applies without prejudice to mandatory law.
1.2. Operator and Legal Status
The operator of SASAHUB is SHAMUS E-TİCARET LOJİSTİK VE GIDA TİCARET LİMİTED ŞİRKETİ. SASAHUB is an electronic-commerce platform and, by that status alone, is not a bank, payment institution, electronic-money institution or payment-system operator. Any payment service for which law requires authorisation or a licence is provided only through an authorised bank, licensed payment/e-money institution or another model expressly permitted by law.
1.3. No Authority to Hold Customer Funds Under This Policy
This Policy by itself does not authorise SHAMUS to receive, safeguard, retain, transfer or otherwise control User funds as a licensed payment service provider. Any model involving possession or control of customer funds may be launched only after a separate legal and technical review and, where required, through an authorised payment partner.
1.4. Related Documents
This Policy applies together with the Terms of Service, Buyer Policy, Seller Policy, Refund & Return Policy, Privacy Policy, Information Security Policy, AML/KYC Policy, Export Control & Sanctions Policy and other officially published SASAHUB documents. The Pricing & Fees Policy applies only after its official approval and publication.
1.5. Applicable Law
For payment processes governed by the law of Türkiye, relevant rules include, among others, Law No. 6493 on Payment and Securities Settlement Systems, Payment Services and Electronic Money Institutions, regulations of the Central Bank of the Republic of Türkiye (TCMB), Law No. 6502, Law No. 6563, foreign-exchange, tax and other applicable legislation. Mandatory rules prevail over this Policy.
Section 2. Definitions
2.1. Payer and Payee
Payer means the person initiating a payment on a lawful basis. Payee means the person legally entitled to receive the relevant amount under a Transaction or another lawful basis.
2.2. Payment and Payment Transaction
Payment means performance of a monetary obligation. Payment Transaction means the actions involved in initiating, authorising, processing, confirming, executing, cancelling or refunding a payment.
2.3. Payment Service Provider
Payment Service Provider means a bank, licensed payment institution, electronic-money institution, acquirer or another provider legally authorised to provide the relevant payment service. Its services are governed by its own terms and applicable financial law.
2.4. Prepayment and Partial Payment
Prepayment means all or part of an amount paid before the principal performance is due. Partial/milestone payment means payments allocated to stages or dates under the Transaction.
2.5. Refund and Chargeback
Refund means the return of money under the Refund & Return Policy, law, Transaction terms or agreement of the parties. Chargeback is a separate procedure for disputing a card transaction through the issuing bank and payment scheme; the relevant financial infrastructure, not SASAHUB, decides that procedure.
2.6. Subscription and Recurring Payment
Subscription means paid access to a service for a fixed or renewable term. Recurring Payment means a subsequent automatic charge based on the User's valid consent/mandate and the payment provider's rules.
Section 3. SASAHUB Payment Models
3.1. Direct Payments Between Users
Where a Transaction provides for a direct bank transfer from the Buyer to the Seller, the parties are responsible for the accuracy of account details, legality of the payment and confirmation of receipt. The fact that the Transaction was arranged through SASAHUB does not make the Operator the recipient or custodian of those funds.
3.2. Integrated Payment Provider
Where the Platform integrates a payment service, the regulated payment operation is performed by the relevant authorised provider within the scope of its permissions. SASAHUB may transmit information needed to initiate the payment and display its status, but does not replace the regulated provider.
3.3. Payments for SASAHUB's Own Services
Payments for subscriptions, service fees, consulting, export, logistics or other services provided directly by SHAMUS may be received by the Operator as the contracting party for those services. Such payments are distinct from funds owed to a Seller under a User-to-User Transaction.
3.4. Escrow and Safe-Transaction Services
Reference to Escrow or a safe-transaction service does not mean that such a service is currently operated or licensed by SASAHUB. It may be launched only after separate approval of the model, adoption of specific terms and compliance with payment-services law, including use of an authorised provider where required.
3.5. Off-Platform Payments
Where Users voluntarily settle outside SASAHUB's integrated payment infrastructure, the Operator does not control the payment and cannot guarantee its execution or refund. Mandatory duties imposed on the Operator by law remain unaffected.
Section 4. Payment Methods
4.1. Bank Transfers
Payment may be made by bank transfer where permitted by the Transaction terms and applicable law. Before sending funds, the Payer must verify the payee, IBAN/account details, amount, currency and payment reference.
4.2. Payment Cards and Digital Wallets
Card and other integrated electronic payments are available only where the relevant provider has been connected. Authorisation, acquiring and other regulated activities are performed by the payment provider under its own rules.
4.3. Prepayment and Milestone Payments
The parties may agree full prepayment, partial prepayment, milestone payments or payment after performance where lawful. The prepayment percentage, due date and trigger for each payment should be clear before the obligation arises.
4.4. New Payment Methods
Open Banking, QR, payment links, tokenised payments and other technologies may be used only after official implementation. This Policy is not a promise that any particular payment method will be available.
Section 5. Payment Processing
5.1. Pre-Payment Information
Before payment confirmation, the User is provided with material information available in the relevant service: payee, amount, currency, payment purpose, applicable SASAHUB fees, payment method and, where relevant, refund or subscription terms.
5.2. Initiation and Authentication
A payment is initiated by an active action of the User. Depending on the provider, 3-D Secure, OTP, banking-app confirmation, MFA, biometric or other lawful authentication may be used. SASAHUB support must not ask a User to disclose CVV, PIN or a one-time banking code by email, chat or telephone.
5.3. Payment Statuses
The Platform may display statuses such as “pending”, “initiated”, “processing”, “successful”, “declined”, “on hold”, “refunded” or another status. Status information is informational and is based on data received from the payment infrastructure.
5.4. Time of Performance
Initiating a payment or seeing a debit does not always mean that the monetary obligation has been finally discharged. The time of performance is determined by the contract, applicable law and confirmation of the relevant bank or payment provider.
5.5. Electronic Evidence
To the extent permitted by law, a transaction identifier, bank confirmation, payment-provider notice, system status, timestamp and other electronic records may be used as evidence. They are assessed together with other evidence and are not automatically conclusive.
Section 6. Fees, Pricing, Taxes and Currency
6.1. SASAHUB Fees
Where SASAHUB charges its own commission or service fee, the User receives information about the amount or calculation method before accepting the corresponding payment obligation, unless law permits otherwise.
6.2. Third-Party Fees
Banks, acquirers, correspondent banks and payment providers may charge their own fees. SASAHUB does not set those tariffs and must not present a third-party fee as its own fee.
6.3. Pricing & Fees Policy
After official approval, the Pricing & Fees Policy governs SASAHUB tariffs, subscriptions and fees to the relevant extent. Until that document is published, prices and terms actually disclosed to the User before the relevant agreement is concluded apply.
6.4. Currency and Conversion
Payment currency is determined by the Transaction, availability of the payment method and law. Where conversion is required, the exchange rate and any markup are determined by the relevant bank or payment provider unless expressly agreed otherwise.
6.5. Taxes
Each party is responsible for its own tax obligations unless law imposes withholding, reporting or remittance duties on another party or the Operator. This Policy does not constitute tax advice.
Section 7. International Payments
7.1. Cross-Border Payments
An international payment may depend on correspondent banks, foreign-exchange controls, the countries of the Payer and Payee, the purpose of payment and other requirements of the relevant jurisdictions.
7.2. Documents and Payment Purpose
A bank or payment provider may request a contract, invoice, information about goods, source of funds, beneficiary or payment purpose. The User must provide accurate information and must not disguise the true economic purpose of the Transaction.
7.3. Sanctions and Export Restrictions
A payment must not be used to circumvent mandatory sanctions, export controls or other prohibitions. Where a transaction is blocked or requires enhanced review under a mandatory rule, the parties must not artificially split, reroute or disguise it to avoid the restriction.
7.4. Timing and Exchange-Rate Risk
SASAHUB does not guarantee the timing of an international bank transfer or the conversion rate where controlled by an independent financial institution. Users should account for possible delays and exchange differences when agreeing Transaction terms.
Section 8. Security and Fraud Prevention
8.1. Protection of Payment Data
SASAHUB applies reasonable security measures within its own infrastructure. Where card payments are processed by an external provider, full card data should be handled by the relevant authorised service in accordance with applicable security requirements; this Policy does not claim that SASAHUB itself is PCI DSS certified unless such certification has actually been obtained.
8.2. User Responsibilities
The User must protect the account and payment instruments, use official channels, verify the domain/payee and immediately contact the bank if compromise is suspected. SASAHUB must never request a PIN, full CVV or OTP by email, chat or telephone for “refund verification”.
8.3. Fraud Screening
SASAHUB and a payment provider may apply risk-based checks, technical limits and anomaly analysis. Measures are applied within the limits of authority, necessity and law and may require additional verification.
8.4. Suspension
A provider may suspend or decline a transaction; within its technical authority the Platform may also block initiation where there are objective fraud indicators, a legal requirement, a sanctions restriction or a material security risk.
8.5. Incidents
In a material payment or information-security incident, SASAHUB may temporarily disable the affected integration, preserve technical logs, notify affected Users where required, and cooperate with the provider or competent authority within the limits of law.
Section 9. Refunds
9.1. Basis
Whether a right to a Refund exists is determined primarily by the Refund & Return Policy, mandatory law, Transaction terms and agreement of the parties. This Payment Policy governs the technical and financial execution of a refund right once established.
9.2. Refund Method
Unless law or the payment provider requires otherwise, a refund is generally sent to the original payment instrument. Replacing a monetary refund with Platform credit, a bonus or credit note is permitted only where there is a lawful basis or the User's valid consent.
9.3. Currency and Amount
A refund is generally made in the currency of the original transaction. Exchange differences or an independent provider's fee are addressed according to law, the reason for the refund and provider rules; a mandatory consumer refund amount may not be unlawfully reduced.
9.4. Timing
SASAHUB and the relevant party initiate a refund within the period required by law or contract. After proper initiation, actual crediting may depend on the bank or payment provider; this does not extend a statutory deadline imposed on the party responsible for initiating the refund.
Section 10. Erroneous or Declined Payments and Chargeback
10.1. Erroneous or Duplicate Payment
For an erroneous or duplicate charge, the User should report the transaction identifier, date, amount and payment method as soon as possible through an official SASAHUB channel and/or to the relevant bank. An objectively verified duplicate payment is corrected in accordance with law and provider rules.
10.2. Declined or Incomplete Payment
Insufficient funds, bank refusal, failed authentication, sanctions screening, a technical error or another factor may prevent payment. Until payment is confirmed as finally executed, the parties should not assume that final payment has occurred.
10.3. Chargeback
A chargeback is initiated through the issuing bank and reviewed under bank and payment-scheme rules. SASAHUB may provide documents relating to the Transaction but does not make the final chargeback decision and does not guarantee the outcome.
10.4. No Double Recovery
A User may not obtain both a full Refund from the Seller and final reimbursement of the same amount through chargeback or another mechanism. If duplicate recovery is identified, the parties may seek correction within the limits of law.
Section 11. Subscriptions and Recurring Payments
11.1. Subscription Terms
Before a subscription is entered into, the User is informed of the plan, term, price, payment frequency, renewal and termination conditions. The subscription begins only after an active action indicating acceptance of those terms.
11.2. Automatic Charging
A one-time payment does not constitute consent to future recurring charges. Automatic charging is permitted only under a valid User mandate/consent and in accordance with provider rules and applicable law.
11.3. Cancelling Automatic Renewal
The User should have an accessible method to disable future automatic renewal within the service functionality and mandatory rules. Cancellation of a future renewal does not eliminate a valid obligation already accrued for the current period unless law provides otherwise.
11.4. Price Changes
A plan-price change applies to a future period after proper notice and, where required by law or the terms, renewed User confirmation. A period already paid for is not retroactively worsened.
11.5. Discontinuation of a Subscription Service
If SASAHUB discontinues a paid service before the end of a paid period, the consequences are determined by the plan terms, Refund & Return Policy and mandatory law. Any applicable special Consumer rights to termination or refund remain preserved.
Section 12. KYC/KYB, AML/CFT and Compliance
12.1. Risk-Based Checks
SASAHUB may conduct KYC/KYB, sanctions and anti-fraud checks to the extent necessary for security, legal compliance, payment-partner requirements or a specific service. The existence of such checks does not by itself mean that SHAMUS is an obliged entity under every AML/CFT regime.
12.2. Payment-Provider Checks
A bank or licensed payment provider may impose its own mandatory requirements concerning identity, source of funds, beneficial owners and payment purpose. SASAHUB cannot waive those requirements.
12.3. No Circumvention
A User must not provide false information, use nominees, artificially split operations or choose opaque routes to circumvent a lawful review. SASAHUB may restrict the relevant function until review is completed, within the limits of law and the Terms of Service.
12.4. Compliance Data Sharing
Information is shared with a payment provider or competent authority only where there is a legal basis and in accordance with the Privacy Policy. The scope is limited to data necessary for the relevant lawful purpose.
Section 13. Liability and Payment Disputes
13.1. User Responsibility
The Buyer is responsible for the accuracy of payment information and timely payment; the Seller is responsible for correct account details, lawful receipt of payment and performance of its obligations after payment. Each party must reasonably mitigate the consequences of its own error.
13.2. Operator Liability
The Operator is responsible for its own actions, infrastructure and mandatory duties within the limits of law and the relevant contract. Liability exclusions or limitations do not apply where liability cannot be excluded or limited by mandatory law.
13.3. Independent Financial Institutions
Delay, refusal, conversion rate or another action of an independent bank/provider falls within that institution's sphere of responsibility unless the issue was caused by a SASAHUB breach. This does not limit a User's right to require SASAHUB to perform its own obligations.
13.4. Payment Dispute
For a payment complaint, the User may provide the transaction identifier, date, amount, currency, payment method and supporting documents. Where the dispute concerns the underlying Transaction, the Dispute Resolution & Complaints Policy and Refund & Return Policy also apply.
13.5. Competent Authorities
A Consumer retains rights to apply to a Tüketici Hakem Heyeti, Tüketici Mahkemesi and other competent authorities where the relevant conditions and monetary thresholds apply. A User may also contact a bank, payment provider or financial regulator on matters within their competence.
Section 14. Contacts and Secure Communications
14.1. Payment Matters
Official email for payment and monetary-refund matters: finance@sasahub.com.tr. General support: support@sasahub.com.tr. Complaints: complaints@sasahub.com.tr. Security: security@sasahub.com.tr. Legal matters: legal@sasahub.com.tr.
14.2. Information for a Request
Users are encouraged to provide the order/Transaction number, payment transaction identifier, date, amount, currency, payment method and supporting document. Only where necessary and safe may the last four card digits be provided. Do not send a full card number, CVV/CVC, PIN, password or OTP.
14.3. Operator Details
SHAMUS E-TİCARET LOJİSTİK VE GIDA TİCARET LİMİTED ŞİRKETİ Address: Cevizli Mahallesi, Mustafa Kemal Caddesi, Hukukçular Towers Sitesi, A Blok, No: 66A, İç Kapı No: 111, Kartal / İstanbul, Türkiye. MERSİS: 0768110028600001 · Trade Registry No: 1114861 · Tax ID (VKN): 7681100286 · Kartal Tax Office. Website: https://sasahub.com.tr
Section 15. Versioning and Final Provisions
15.1. Version Control
10.08.2026. Effective date: date of official publication. Planned review: no later than 12 months or earlier following a material change in law, payment architecture or functionality.
15.2. Language Versions
The Turkish text is the official controlling version. Russian and English are official published translations. Mandatory applicable law prevails regardless of the language of this document.
15.3. Change of Payment Model
Integration of a new payment provider, holding customer funds, launch of Escrow, marketplace payouts, e-money, acquiring or another materially new financial model requires a separate legal, contractual, compliance and technical review before launch.
15.4. Policy Amendments
A new version is officially published. Amendments for which law requires advance notice, separate consent or a new payment mandate cannot become effective merely through silent continued use of the Platform.
15.5. Final Provision
This Payment Policy governs the financial aspects of using SASAHUB but does not replace the contract between Buyer and Seller, the rules of a licensed payment provider or mandatory financial law.
Corporate Approval
For and on behalf of SHAMUS E-TİCARET LOJİSTİK VE GIDA TİCARET LİMİTED ŞİRKETİ SHAMIL TEMIEV Şirket Müdürü · Münferiden Temsile Yetkili Signature: __________________