TSYS review

TSYS Total Issuing is a commercial card issuing and processing platform from FIS, positioned as API-first and cloud-native. It sits behind banks’ and fintechs’ payment applications: the platform supplies issuing capabilities, transaction processing, fraud management and program data, while APIs connect those services to an organization’s applications.

It is intended for consumer and commercial card programs, including credit, debit, prepaid, health care, loyalty, installment and buy now, pay later. The product also covers digital and virtual card issuance, commercial spending controls, transaction insights and fraud scoring. FIS describes a scalable architecture built around microservices and extensible plug-ins, with real-time authorization and intelligent routing.

This is infrastructure for organizations operating payment programs, not a developer library or a self-serve merchant checkout tool. Before selecting it, map which parts of the issuing stack TSYS will own, how its APIs fit your existing services, and which processing and operational responsibilities remain with your team.

FIS describes Total Issuing as API-first, with open and flexible APIs for integrating card-issuing capabilities, data and services into applications. The page also describes microservices, extensible plug-ins, configurable workflows and real-time data access. These are the named integration surfaces; it does not identify a protocol such as REST or GraphQL, nor document webhooks or a CLI.

The vendor doesn't publish named SDKs or supported programming languages on the product page. Confirm SDK availability, authentication, API versioning, sandbox access, webhook support, error handling and rate limits in FIS’s developer documentation and during technical evaluation. The product page links to a Developers area, but does not give enough implementation detail to estimate integration effort from the overview alone.

For a production design, ask for API references and example flows for issuance, authorization, transaction updates and fraud workflows. Also establish how API changes are versioned and whether your team can test end-to-end flows before a program goes live.

The pricing page lists no public plans or starting price. FIS services and processing rates are custom-quoted and contracted individually; the pricing page text gives no monthly or annual billing terms. It lists no free plan or free trial, so teams should not budget on a self-serve evaluation tier.

The public pricing information does not give a per-transaction rate, minimum commitment, implementation fee, usage band, seat charge, overage rate or add-on price. That leaves the main production cost drivers to resolve in a quote. Ask FIS to separate platform fees, processing charges, program setup, support, fraud services and any costs tied to transaction volumes or additional capabilities. Get the pricing model and renewal terms in writing, including how rates can change and how fees apply to inactive programs.

Merchant-processing complaints on Reddit include reports of unexpected fees, but those posts do not establish Total Issuing’s pricing or contract terms. Compare a detailed TSYS quote against your expected program volumes and card mix rather than using those anecdotes as a rate estimate.

Total Issuing is a proprietary FIS commercial platform, not a public open-source project. FIS describes cloud-native capabilities, but does not publish a customer self-hosting option or an open-source licence. Ask FIS which deployment models are available for your program and where transaction data is stored and processed.

The product page describes real-time data access, transaction insights and portfolio analytics, but it does not describe a data-export process or migration tooling. Confirm what data you can export, in which formats, how often, and whether you can retrieve historical authorization, settlement and fraud records after ending a contract.

Expect migration to involve more than replacing an API endpoint: card programs, processing workflows, fraud rules and connected applications may need to move together. Before signing, document data ownership, export rights, transition support, contract exit terms and the work required to transfer active card accounts to another processor.

FIS positions Total Issuing for scalable processing, real-time authorization, fraud scoring and digital wallet provisioning. Before relying on those capabilities, get service-level commitments, incident procedures, disaster-recovery terms, availability targets and operational support coverage in the contract. Confirm transaction and API limits, latency expectations, retry guidance and how the platform handles outages; the product overview does not provide numeric limits or reliability targets.

Security and compliance responsibilities also need to be explicit. Ask which controls FIS operates, what your organization must implement, and how access, cardholder data, fraud cases and audit records are handled. Test failure paths such as delayed transaction updates, rejected requests and interrupted provisioning in a vendor-supported environment.

Reddit users discussing TSYS merchant processing report fee disputes, held funds and recurring charges after processing stopped. Those are anecdotal merchant-account reports, not proof of how Total Issuing performs or what its contracts require. They are a reason to scrutinize statements, risk reviews, reserve and hold terms, escalation paths and account-closure procedures.