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).
  • Fully secured and PCI compliant.

System Integration​

Ingress​

  • Can run as a standalone web app or embedded in a CRM.
  • Data can be proxied via query string parameters.
  • Any provided field 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
    • Redirect to a known location
    • Display relevant fields to the agent

Live Agent Journeys​

Flow & Launch​

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

Correlation​

To link the agent’s web session with the customer call (correlation):

  • Automatic: If the parent app (e.g. CTI bar) passes call metadata.
  • Manual:
    • DTMF: Agent types generated digits into their handset (e.g. #974##)
    • 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).
  • Once valid, Submit becomes active.

Completion​

On form submission, configurable actions include:

  • Payment – Authorisation/Tokenisation request to PSP
  • Datapost – Send non-card data to an endpoint
  • Redirect – Forward to endpoint with non-card data
  • Completion screen – Show result to agent (skipped if redirect used)

Digital Channel Journeys​

Flow & Launch​

  • Agent launches Transact via a web link with account reference + configuration.
  • 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​

Same as live agent journey: Payment, Datapost, Redirect, or Completion screen.