Transact 2026.8 - New Payment Providers, Data Poster, and Continued platform improvement

Transact 2026.8 is here: four new payment provider integrations, a brand-new Data Poster service, richer agent and customer payment journeys, and a solid layer of security and platform work underneath.

This release broadens the range of payment providers you can transact through, adds a dedicated service for delivering transaction data to your own endpoints, and continues to harden the platform around security, compliance, and reliability. There is also a lot of groundwork in the payment adapter and call-correlation flows that makes day-to-day operation more predictable.

Highlights

• Four new or expanded PSP integrations: Adyen, Verifone (Commidea), Stripe, and Trust.
• New Data Poster service for delivering transaction data to customer endpoints under a strict API contract.
• Agent and Customer UI v2 complete UI refresh including new Pay by Manual Entry and performace improvements for Pay by Link.
• Stronger data protection with customer-specific encryption.
• New in-flight call correlation checks, including automatic clearing of stale calls.
• OpenAPI/Swagger documentation added and updated across all PSP, card-capture, and auth endpoints.

New Payment Provider Integrations

Transact 2026.8 significantly expands the set of payment providers available through the adapter.

• Adyen — Full Adyen integration.
• Verifone (Commidea) — Full Verifone Commidea integration.
• Stripe — Full Stripe integration.
• Trust — Full Trust integration.

For endpoint details, see the Adyen, Stripe, Trust, and Verifone Commidea references in the Transact API documentation.

New Data Poster Service

A new Data Poster service delivers transaction data to customer endpoints under a strict API contract. It supports server-side data posting, including a "from-server" proxy flow and input-parameter fallbacks, so data can be delivered reliably even when the calling context is incomplete.

• Dedicated service for posting transaction data to customer endpoints.
• Strict API contract for predictable integration.
• Server-side datapost with a "from-server" proxy flow and input-parameter fallbacks.

Data Protection Enhancements

Data protection gains customer-specific handling in this release.

• Added customer-specific encryption and decryption methods.
• Generic encryption/decryption added to the data-protection service for broader reuse.

Payments and Adapter Enhancements

The payment adapter continues to mature, with more routing and mapping now driven consistently through the adapter.

• Zero-pence (account verification) authorisations are now routed through the adapter.
• ISO currency-code support and corrected auth-only payment mappings.
• Card-type override and credit-card restriction handling driven from session data.

Agent and Customer UI

The agent and customer payment experience moves to v2, with a number of usability and correctness fixes.

• UI v2 rollout with migration to Faro observability.
• Pay by Manual Entry form added, with corrected card/Luhn validation, expiry validation, and accurate digit counting and masking.
• Pay by Link improvements — form bindings, and SMS/email link fields pre-populated from the supplied billing email and phone.
• Pay by Link can optionally render the payment link as a scannable QR code, controlled by a dedicated AllowQrCode setting (off by default).
• Customer cancel feedback (tooltip/marker) and clearer invalid-length validation warnings.
• Masked card values are now preserved across capture-mode switches and after inactivity timeouts.
• Agent notification timing and email validation fixes, plus customer UI load-time improvements.

Call Correlation

Manual correlation is now gated on live call activity, making correlation safer and cleaner.

• Manual correlation is gated on an active call.
• Accounts can report whether they have live calls.

Security and Compliance

A meaningful part of this release focuses on tightening security and reducing exposure.

• Added generic encryption/decryption to the data-protection service.
• For PSPs that require it, stored payment responses are now namespaced by account.
• Outbound HTTP calls no longer reuse default headers, preventing header and data leakage.
• Vulnerable dependencies patched.
• Audit-logging improvements.

API Documentation and Platform

The reference documentation and build platform have both had significant attention.

• OpenAPI/Swagger documentation added and updated across all PSP controllers, card-capture, and auth endpoints.
• New release process and build pipeline.
• Removal of legacy and unused components.

For the full set of endpoints, see the Transact API reference.