Skip to main content

Transact

Subphonic Transact helps you meet PCI DSS standards when handling card payments over the phone or digital voice channels.
It keeps your agents out of scope while protecting your customers.

  • Supports payments via voice IVRs, live agents, and digital channels (chat, SMS, and email).
  • Fully secured and PCI compliant.

It starts with your payment flow​

Whatever payment journey you run today, Transact sits in the middle to keep sensitive card data away from the agent while preserving a smooth customer experience.

Interactive masking flow

Customer
1
▶
Subphonic
▶
Agent

1 / 3Customer enters raw keypad input

A raw keypad digit (1) begins on the customer side.

System Integration​

It all starts with your payment flow. Transact is designed to fit around it, whether you run phone payments in a contact centre, inside Teams, in a CRM desktop, or through API-led IVR journeys.

Getting data in​

  • Run Transact as a standalone web app or embed it in platforms such as CRM tools or Microsoft Teams.
  • Pass context through URL/query parameters (for example: customer reference, order ID, amount, or agent identity).
  • Use inbound values to pre-populate agent-visible fields and carry required metadata into payment processing.

Getting data out​

On completion of capture or payment, Transact can:

  • Send data via HTTP POST from either the browser or datapost service.
  • Redirect to a known destination in your journey.
  • Display relevant completion fields directly to the agent.

Integration examples​

  • Sales teams: Launch from CRM or Teams with pre-filled context so agents can take payment immediately.
  • Security and compliance teams: Keep card data off agent devices and recordings while maintaining PCI DSS-aligned controls.
  • Developers: Connect Transact to existing APIs and workflows using launch parameters, POST callbacks, and redirects.

Live Agent Journeys​

Flow & Launch​

  • Agent triggers Transact launch via a web link.
  • The URL contains:
    • Account reference
    • Configuration name (maps to JSON file describing the journey, fields, PSP integration).
    • Agent name
  • Agent selects “Pay by Phone” to begin.

Correlation​

The method of linking the agent’s web session with the customer call:

  • Automatic: Transact can automatically correlate if the parent app (e.g. Teams Call) passes call metadata.
  • Manual:
    • DTMF: Automatically generated digits (e.g. #974##) are typed into the agent's handset.
    • Search: Agent searches for the live call and selects it.

Once correlation succeeds, the capture screen loads.

Capture​

  • Agent requests the customer to enter card details via their handset.
  • Real-time capture status updates shown.
  • Card scheme validated (PAN length, CSC).
  • Luhn check performed.
  • Once valid, Submit becomes active.

Completion​

On form submission, configurable actions include:

  • Payment – Request to PSP
  • Datapost – Sends configured transaction information to the designated endpoint
  • Redirect – Navigates to the designated endpoint with configured transaction information
  • Completion screen – Show capture/PSP result to agent

Digital Channel Journeys​

Flow & Launch​

  • Agent triggers Transact launch via a web link.
  • The URL contains:
    • Account reference
    • Configuration name (maps to JSON file describing the journey, fields, PSP integration).
    • Agent name
  • Agent selects “Pay by Link” to begin.

Channel​

  • Depending on configuration, the agent chooses a channel (e.g. SMS, chat) to send the secure link.

Capture​

  • Customer opens the link; agent’s screen switches to capture view.
  • Capture page can include branding and use the customer’s domain.
  • Customer enters card details manually or via browser autofill.
  • Only when both sides (customer + agent) complete mandatory fields does Submit activate.

Completion​

On form submission, configurable actions include:

  • Payment – Request to PSP
  • Datapost – Sends configured transaction information to the designated endpoint
  • Redirect – Navigates to the designated endpoint with configured transaction information
  • Completion screen – Show capture/PSP result to agent

IVR Channel Journey​

Flow & Launch​

  • IVR establishes Transact capture session via Transact API
  • The API contains:
    • JWT
    • sipCallId (The Id of the Call to secure).

Capture​

  • IVR requests the customer to enter card details via their handset.
  • IVR is sent zeros in place of DTMF tones
  • Card scheme validated (PAN length, CSC).
  • Luhn check performed.
Docs AssistantAsk anything about our products