Skip to main content

Transact

Aiphoria 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.

System Integration​

Ingress​

  • Can run as a standalone web app or embedded within an existing system such as a CRM or MS Teams implementation.
  • Data can be proxied via query string parameters.
  • Any provided data can be displayed to the agent or passed to the PSP.

Egress​

  • On completion of capture or payment, Transact can:
    • Send data via HTTP POST from either the browser or datapost service
    • Redirect to a known location
    • Display relevant fields to the agent

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 ditits (e.g. #974##) are typed into the Agents 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.