Techbanq

Cybersecurity · payments

The best card-data control is not holding the card data

Every system that touches a card number inherits the obligations that come with it — the segmentation, the logging discipline, the audits. Engineering a payment environment therefore starts with subtraction: redirect capture to the processor, tokenise on entry, and let most of your estate never see a card at all. Then harden the little that remains.

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

Workstation showing terminal output during a security review

Enterprise delivery credentials

  • National Cybersecurity Authority, Saudi Arabia

    NCA registration

    Registered cybersecurity service provider

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

Scope minimisation

Tokenise, redirect, never touch: the order that shrinks a payment estate

Each step removes systems from the environment that has to be defended and audited. The fallback exists because some businesses have a channel that genuinely must touch cards — and it is fenced, not scattered.

A flow of four steps — redirect capture to the processor, tokenise at the boundary, confine what remains, harden the remainder — with a fenced branch for channels that must still touch cards.

  1. 01

    Redirect the capture

    The card form is the processor's — a hosted page or hosted fields — so the number is typed into their environment, not yours. Your servers never receive it, which is the single largest subtraction available.

  2. 02

    Tokenise at the boundary

    What comes back is a token: useful for refunds, repeat billing and reporting, worthless to a thief. Everything inward of the boundary works in tokens and drops out of the defended environment.

  3. 03

    Confine what remains

    If any component must still handle card data — a vault, a capture relay — it is made small, single-purpose and reachable only through one narrow, watched interface.

  4. 04

    Harden the remainder properly

    The small environment left is where the full discipline concentrates: segmentation, monitored access, clean logging, managed keys. Small scope is what makes real rigour affordable.

Always available

The channel that must touch cards

A call centre taking payments by phone, a legacy integration that cannot use tokens — these are fenced into their own bounded environment with their own controls, rather than being allowed to pull the whole estate back into scope.

The boundary

A payment boundary is proven by traffic, and a log is clean by design

Segmentation of a cardholder environment fails in a characteristic way: the diagram shows an island, and the network shows a peninsula. A monitoring agent reaches in, a backup job reaches out, a shared database serves both sides, an administrator's workstation bridges everything — and each connection quietly extends the defended environment to whatever it touches. So the boundary is treated as a claim to be tested, not a fact to be drawn: enumerate every path in and out, justify each one or close it, and then demonstrate with observed traffic that nothing else crosses. A boundary that has been probed from the outside and watched from the inside is evidence; a boundary that exists in a diagram is an intention.

Logging inside a payment environment carries a paradox: the investigation needs rich telemetry, and the one thing the telemetry must never contain is the card data itself. Card numbers leak into logs by accident, not policy — a full request body captured on an error, a debug flag left on after an incident, a crash dump that snapshots memory. Once there, the logging pipeline becomes the largest unprotected copy of the data the whole architecture exists to confine, replicated into every analytics tool and backup downstream. The engineering answer is structural: log events and identifiers rather than payloads on the payment path, mask at the point of capture rather than trusting later scrubbing, and test the pipeline the way an attacker would read it — by searching the logs themselves for card patterns, on a schedule, forever.

Key management

A cryptographic key is a lifecycle with a custodian, not a setting

Encryption in a payment environment is only as strong as the management of its keys, and key management is a category of work with stages, owners and evidence — not a checkbox on a storage service.

Generation and custody

Keys are generated inside hardware or a managed key service, never on a laptop; custody is split so no single person holds a usable key alone, and every key has a named owner.

The evidence it leaves: A key inventory that says who can use what, provably.

Use and separation

Each key has one job — data at rest, transport, signing — and the systems that use a key never see it, calling the vault or module for the operation instead of holding the material.

The evidence it leaves: A compromise of one system that does not surrender the keys.

Rotation and rollover

Rotation is rehearsed as an operation, not feared as an outage: new key in, old key kept for decryption of existing data, cutover verified, all on a schedule that does not wait for a compromise.

The evidence it leaves: A rotation log showing the schedule is real.

Retirement and compromise response

Retired keys are destroyed with a record, and the emergency is designed in advance: if a key is suspected compromised, the path to revoke, re-encrypt and re-issue is written down and has been walked once.

The evidence it leaves: A key emergency that is a procedure, not a project.

Our role

What we engineer around card data and where the formal assessment begins

This work maps naturally onto PCI DSS, whose requirements follow the same logic — confine the data, defend the boundary, control the keys, keep the evidence. We build to that logic; the standard's formal machinery stays with the parties it belongs to.

  1. 01

    The scope, engineered down

    We design and implement the subtraction — hosted capture, tokenisation, the vault boundary — so the environment that has to be defended is as small as your channels allow.

  2. 02

    The remainder, defensible

    We build the segmentation, access, logging and key disciplines on what remains, each producing its own evidence as it runs, so demonstrating the control is a byproduct of operating it.

  3. 03

    The readiness, not the verdict

    Where PCI DSS validation is required, we prepare the environment and its evidence for the assessment, and the assessment itself is performed by a qualified assessor — a role we do not hold and do not imitate.

Which payment channels the business keeps, and which legacy integrations are worth the scope they drag in, are commercial decisions; we put the cost of each in front of you in systems and obligations, so the choice is made with the price visible.

Common questions

What buyers ask

If card capture is fully outsourced to our processor, is the security work done?+

It is dramatically reduced, not done. Hosted capture removes the card number from your servers, which is the biggest single win available — but three surfaces stay yours. The page that embeds the processor's form is yours, and a script injected into it can repaint or overlay that form; payment-page integrity remains your problem. The tokens are yours: a token cannot be sold like a card number, but a system that can use tokens can still refund, re-bill and redirect value, so token-using systems need real access control. And the configuration is yours — the API credentials to the processor, the webhook endpoints, the staff accounts on the processor's dashboard are all attack paths that outsourcing created rather than removed. Outsourcing capture is the right first move; it changes what you defend, not whether you defend.

Do you carry out PCI DSS assessments yourselves?+

No, and the boundary is worth stating precisely. Formal PCI DSS validation is performed by Qualified Security Assessors — firms accredited by the PCI Security Standards Council — or through self-assessment where the card schemes and acquirers permit it. Techbanq is not a QSA, does not issue attestations, and cannot certify an environment as compliant. What we do sits before and after that line: engineering the environment so the scope is small and the controls are real, assembling the evidence an assessment will examine, and remediating what an assessment finds. Teams that arrive at a formal assessment with the architecture already shrunk and the evidence already flowing spend the assessor's time confirming rather than discovering, which is the cheap way to spend it.

Our call centre takes card payments over the phone — does that put everything in scope?+

Only if it is left woven into everything else, which is the usual mistake. A phone payment channel means card numbers are spoken aloud and typed by agents, which brings the agents' desktops, the telephony platform and any call recording into the defended environment. The engineering answer is to fence it: route the moment of card entry away from the agent where possible — pause-and-resume recording paired with the customer keying digits into the phone system, or a payment link sent mid-call — and where the agent must handle the number, confine those workstations to their own segment with no path to the wider corporate network. Done well, the phone channel becomes a small bounded environment with its own controls; done casually, it quietly makes the whole office part of the payment estate.

Next step

Shrink your scope with us

An architecture review that traces where card data can currently exist in your estate, how much of that footprint subtraction can remove, and what the remaining environment needs to withstand scrutiny.