Skip to main content

Application Architecture

Transact is built on Azure as a set of microservices fronted by an Application Gateway. All traffic — web UIs, APIs, and telephony — enters through a single secure edge, and an event-driven Service Bus keeps services decoupled. A PSP Adapter layer abstracts payment providers so multiple acquirers can be used without changing upstream logic.

Each Transact deployment runs inside its own Azure subscription and can be provisioned in different Azure regions or locations to meet data residency, latency, or compliance requirements.

Transact supports two payment channels, each following the same core pattern but with a different customer-facing experience.

Phone Payment​

During a phone payment the customer is on a live call routed through Subphonic Tel. The agent initiates payment via the Agent UI, AI Services handle real-time transcription/voice processing, and the Card Capture service securely collects card details while the call is in progress.

Key points​

  • AI-powered — real-time transcription and voice processing run inline on the call.
  • Correlation tracks the live call so card capture stays in sync with the conversation.
  • Push notifications keep the agent informed of payment status without polling.

Digital Payment​

For digital payments the agent sends the customer a unique payment link (via SMS, email, or chat). The customer completes payment on their own device through a Customer UI, while the Remote Card Capture service manages that web session.

Key points​

  • No telephony required — payment happens entirely over the web.
  • Communication Services deliver the payment link via SMS, email, or other digital channels.
  • Remote Card Capture manages the customer's browser session independently from the agent.

Common across both channels​

ConcernHow it's handled
SecurityAzure Application Gateway / Firewall at the edge; Auth service for all identity and access
Payment routingPSP Adapter abstracts provider differences — supports multi-acquirer failover and choice
MessagingAzure Service Bus for event-driven, decoupled communication between services
StateDatabase for persistence; Cache for session and card data
Real-time updatesPush Notification Service streams status changes to the Agent UI