Payment Orchestration

1. Purpose and Scope

This documentation explains how Yocota sits above payment providers, which roles it does and does not take, and how payments, settlement, refunds, records and security work on the Platform.

2. Five-Document Framework

The Yocota legal framework is made of five documents that apply together: the Terms of Service, the Commerce & Supplier Addendum, the Privacy Policy, the Buyer Policy and this Payment Orchestration documentation.

3. Yocota Ecosystem Position

Yocota is commerce and checkout software. It is not a bank, a payment service provider, an acquirer or a money remitter, and it does not offer deposit accounts. Payments are processed by licensed providers.

4. Operating Models

• Direct Settlement (active): the provider processes the payment and settles the seller's share directly into the seller's verified payout account; Yocota receives its commission.
• Yocota Commerce (where enabled): a Yocota entity may act as merchant of record for eligible transactions and record proceeds in the Yocota Balance before payout.
• Connected Provider (where enabled): the seller connects its own provider account and Yocota acts as the checkout and orchestration layer above it.

5. Technology Partner Role

In every model, Yocota provides the technology for products, checkout, delivery, records and buyer protection. Provider-side activities such as authorisation, capture, settlement and card network handling are performed by the providers.

6. No Assumption of Provider Financial Obligations

Yocota does not assume the obligations of providers, banks or card networks, and does not guarantee settlement, approval rates or the availability of any payment method.

7. Provider Responsibility and Third-Party Dependencies

Each provider is responsible for its own regulated services and may approve, decline, hold or reverse payments under its own rules. Downtime or decisions of a provider can affect checkout and settlement.

8. Connected Provider and BYO Gateway Responsibilities

Where a seller connects its own provider, the seller is responsible for its contract with that provider, its credentials, its fees and its compliance, and authorises the Platform to use the related data to operate checkout.

9. Unified Checkout and Branding

Buyers pay through one Yocota checkout page per product, showing the product, seller, price and support details, regardless of the provider used behind it.

10. Payment Method and Route Controls

Payment methods are enabled per country, currency and seller. Card payments are currently available; other methods, such as Stripe, Paystack, M-Pesa and e-Mola, are activated only after provider approval. Yocota may enable, disable or change routes for operational, risk or compliance reasons.

11. Provider Integrations, Credentials and Tokens

Provider credentials are stored only on our servers, are never exposed to the browser and are protected by access controls. Requests to providers use signatures and idempotency keys where the provider supports them.

12. No Direct Storage of Sensitive Card Data

Card details are entered on the provider's secure page. Yocota does not store full card numbers or security codes.

13. Webhooks, Normalised Events and Technical Evidence

Payment outcomes are confirmed by provider notifications (webhooks) whose signatures are verified, or by querying the provider directly. An order is only marked as paid once the provider confirms the payment; pending statuses never release a product.

14. Reconciliation, Ledger and Operational Records

Orders, payment statuses, commissions, refunds and provider references are recorded and periodically reconciled with the provider to close operations whose notification did not arrive.

15. Settlement, Payouts and Provider Outcomes

Under Direct Settlement, payout timing follows the provider's settlement schedule and the seller's bank. Yocota shows the related records in the seller area but does not control the provider's or bank's timing.

16. Refunds, Disputes, Chargebacks and Buyer Protection

Refunds are processed through the provider that took the payment, to the same payment method, in line with the Buyer Policy. Chargebacks follow the provider and card network rules, using the records kept by the Platform as evidence.

17. Risk Review, Product Category Controls and Route Restrictions

Every product is reviewed before sale, and some categories or payment methods may be restricted or unavailable for certain products, sellers or countries.

18. Seller, Supplier and Developer Responsibilities

Sellers must keep product information accurate, deliver what they sell, respond to buyers and keep their payout details current. Anyone using integrations must protect their keys and follow the documentation.

19. API, Sandbox and Production Controls

Test and live environments are kept separate, and credentials from one environment cannot be used in the other. Live operations move real money.

20. Data Protection and Privacy

Personal information is handled as described in the Privacy Policy.

21. Security Responsibilities

Yocota secures the Platform, its servers and its credentials. Sellers secure their own accounts, devices and payout details. Providers secure their own systems and card data.

22. PCI, Tokenisation and Shared Responsibility

Card data security is the responsibility of the PCI DSS-compliant provider hosting the payment page; Yocota's responsibility is to integrate with it securely and never handle raw card data.

23. Regional Activation and Compliance Pathways

New countries, currencies and payment methods are activated only after the relevant provider approvals and compliance checks are in place.

24. TPPP, Payment Facilitation and Regulated Activity Boundaries

Yocota does not hold itself out as a payment facilitator or third-party payment provider. Where a regulated role is needed for a model, it is performed by a licensed provider or only after the required authorisations are obtained.

25. Operational Implementation Controls

Prices are always calculated on our servers from the stored product, never trusted from the browser; amounts and phone numbers are validated before any charge; and no secret, signature or full phone number is written to logs.

26. Audit, Records and Evidence Retention

Transaction, delivery and dispute records are retained for the periods required by law, tax rules and provider dispute windows.

27. Suspension, Limitation and Termination

Routes, payment methods or accounts may be suspended or terminated on the grounds set out in the Terms of Service.

28. Changes to this Documentation

This documentation may be updated as providers, methods and operating models change. The current version is always on this page.

29. Contact

Questions about payments and integrations can be sent to suporte@yocota.com.

Technology and platform:

Yocota LLC, domestic limited liability company (New Mexico registration no. 0008092470), 1209 Mountain Road Pl NE, Ste R, Albuquerque, NM 87110, United States

South African operations:

YOCOTA (PTY) LTD (registration no. 2026/831703/07), 11 Gwezi Street, Dunoon, Milnerton, Cape Town, Western Cape, 7441, South Africa

E-mail:

suporte@yocota.com

Phone / WhatsApp:

+27 81 898 7082

Website:

yocota.com