Approve & Pay, Act, product 5 of 8
The problem. Agent orders can go through at prices nobody approved, twice after a retry, or get disputed with no record of what the customer agreed to.
What changes. Every order is tied to a quote from your systems, the customer’s exact approval and a payment your provider confirmed.
Working in lab runs end to end in our lab todayIn lab on our build plan: designed, being built or tested in our lab; not available yetWhat works today
The customer approves the exact item, price and terms on your page. If the price, availability or a key term changes before the order, the old approval stops counting and the customer is asked again.
Payment happens on your payment provider’s page, which only the customer sees. TrueSession accepts only the provider’s verified result. A browser coming back to a success page never counts as paid.
Each approval can create one order. If the agent retries after a dropped connection, it gets the original result instead of a second order. Every check, approval and payment result is on the order’s timeline.
One customer request, with and without a gateway in front of your systems.
The agent improvises with whatever it can scrape.
The agent reads an old copy of your fares page.
To stay under $600 it books a cheaper, non-refundable fare.
The customer never saw the final fare rules or total.
The trip changes, the customer disputes the charge and you cover the cost.
Result: an unhappy customer, a dispute and a cost you carry.
The agent follows your rules and the customer decides.
The agent is verified at your gateway before it sees anything protected.
It reads the refund rules you reviewed and live prices from your system.
It holds a refundable fare inside the customer’s $600 limit.
The customer approves the exact fare and total, then pays on your page.
The booking, every check and the approval are on your timeline.
Result: a sale the customer chose, with proof of every step.
Each feature with its status today.
No. TrueSession does not process payments. Your customer pays on your existing payment provider’s page, and TrueSession only accepts the provider’s verified result. Agents and TrueSession never see card numbers or one-time passcodes.
Yes, that is one of the industries we are designing for. Agents can ask about products, pay known bills or move money between a customer’s own accounts within limits the customer set. A new payee, a larger amount or an account change always waits for the customer’s exact approval. The bank keeps its own strong customer authentication and core systems.
We are designing pilots with merchants, marketplaces and banks.