TRPOS

TRPOS: An Overview For Merchants

TRPOS is a Turkish payment institution providing card acceptance solutions for businesses that sell online or in person. On its official channels, TRPOS highlights three core products for merchants: Virtual POS for e-commerce, Physical POS for card-present payments, and Payment Link for remote collections.

What TRPOS Offers

Virtual POS (Online Card Payments)

TRPOS provides a Virtual POS for accepting card-not-present payments on websites or apps. The product is positioned to make setup and acceptance secure and fast. For Turkish merchants, Virtual POS is the standard route to accept domestic and international card payments online through a payment service provider.

Key points from TRPOS documentation and pages:

• Processes standard e-commerce “sale” transactions and supports both 3D Secure and a standard flow selectable via the StoreType parameter.

• Accepts installment inputs via the Installment field in requests, which can carry values such as 0 and 2–12.

• Supports multiple currencies at the API level, with enumerations for TL, USD, and EUR.

Physical POS (In-Store Card Acceptance)

TRPOS also offers a Physical POS option for card-present acceptance in retail or on-site environments. While hardware specifications are not listed publicly on the pages we reviewed, the official site positions Physical POS as part of the core solution set. Merchants should request device and certification details during onboarding.

Payment Link (Remote Collection Without a Website)

Payment Link allows a merchant to generate a secure pay-by-link and share it via email, SMS, social channels, or messaging apps. TRPOS states these links are protected and processed under PCI DSS controls. This is useful for invoices, manual orders, or social commerce.

Security, Certification, And Risk Controls

PCI DSS

TRPOS indicates it operates under PCI DSS controls on multiple official pages, including its Payment Link page and site messaging about PCI/DSS. PCI DSS is the global baseline for protecting card data in environments that store, process, or transmit payment account data.

3D Secure

Developer documentation shows merchants can transact using 3D Secure or a standard flow, controlled by the StoreType parameter. Using 3D Secure shifts authentication to the issuer and can reduce fraud and chargeback liability on eligible transactions. For background, 3D Secure is the card-network authentication protocol for online card payments.

Message Authentication And Hashing

Requests in the TRPOS API are signed using HMAC-SHA-512. Hash creation uses merchant keys provided by TRPOS, and responses also include a hash for verification. This mechanism helps prevent tampering and supports integrity checks end-to-end.

Tokenization And Stored Cards

TRPOS exposes a Card Save endpoint. After a card is saved, the API returns a CardToken value to be used later within the PanCode field for subsequent payments, enabling card-on-file transactions without re-entering sensitive data.

Licensing And Legal Basis

TRPOS operates in Turkey as a licensed payment institution. The Central Bank of the Republic of Türkiye (TCMB) issued an activity permit decision for TRPOS Ödeme Kuruluşu A.Ş. on October 5, 2023. TRPOS’s legal pages also reference the applicable Turkish payments law framework. Merchants operating in Turkey should validate their use case and scope under this regime.

Developer Experience And Integration

Core Endpoints And Operations

TRPOS provides a developer site that documents the payment lifecycle. Notable capabilities include:

• Sale: Card-not-present sale with 3D Secure or standard flow; supports Installment, Currency, ReturnUrl, and additional customer fields.

• Void (Cancel): Cancel a transaction before end-of-day closure.

• Refund: Refund after end-of-day closure, with dedicated request and response fields.

• Transaction Query: Retrieve transaction details and status.

• Commission Query: API for merchants to query commission settings by site, returning installment-level commission percentages and card attributes.

These endpoints are documented with request and response examples, including a sandbox base such as vpostest.trpos.com. The documentation shows enumerations for currencies and installment counts, and clarifies when to use 3D Secure.

Supported Currencies And Installments

The API enumerates currency codes for Turkish Lira, US Dollar, and Euro, and includes a dedicated installment field. Installment handling in Turkey is a common commercial requirement, and the presence of these fields suggests TRPOS is designed to work with such flows where permitted by issuers and schemes. Always confirm installment availability per BIN, card program, and sector.

Card-On-File Flows

The Card Save endpoint returns a token that can be reused for future charges through the PanCode field. This is relevant for subscriptions or returning customers. Ensure your handling of stored credentials follows card-brand and local regulatory rules.

Platform Integrations

TRPOS lists e-commerce integrations. The “Integrations” page specifically references WooCommerce, indicating an available connector or guide for that platform. Merchants on other platforms should request documentation or plugins directly from TRPOS.

Pricing, Fees, And Payouts

TRPOS provides an API to query commission settings by merchant site and installment scenario, which indicates fee configuration varies by merchant profile and transaction type. However, a public fee schedule was not available on the official pages we reviewed. To understand commissions, monthly fees, and payout timing, you should contact TRPOS and request a written proposal and settlement calendar.

Implementation Considerations

• Compliance And Scope: TRPOS asserts PCI DSS coverage. Merchants should still implement their own PCI responsibilities, including secure handling of any fields that traverse their systems and proper segregation of keys and secrets. See PCI SSC guidance for responsibilities and validation methods.

• Authentication Choice: Use 3D Secure where appropriate. Many Turkish issuers expect 3D Secure for riskier transactions, and 3DS can affect liability. Confirm 3DS behavior and exemptions with TRPOS and your acquirer.

• Localization: Much of the developer documentation is in Turkish. Ensure your team reviews the latest Turkish materials or requests English documentation where necessary.

• Installments: Although the API supports installment values, eligibility depends on issuer rules and merchant category. Validate installments per card program before going live.

Ideal Merchant Profiles

• E-commerce Businesses In Turkey that need Virtual POS with 3D Secure, card tokenization, and optional installments.

• Sellers Without A Full Web Store who collect payments via links shared on messaging and social channels.

• Retailers And On-Site Sellers who prefer a single provider for both Physical POS and online checkout.

Conclusion

TRPOS is a Turkey-based payment institution offering a unified stack for online, in-person, and link-based payments. Its official materials show PCI DSS controls, a developer API with HMAC-signed requests, 3D Secure support, tokenization for stored credentials, refunds and voids, commission queries, and at least one platform integration reference for WooCommerce. Pricing and some operational details are not published, so merchants should obtain a formal, merchant-specific offer and verify card-brand coverage, settlement terms, and POS hardware specs during due diligence. For Turkish merchants that need installments and a mix of channels under one provider, TRPOS is a candidate worth evaluating based on the documented capabilities and its TCMB activity permit.