OmniArx

Protect the one action that matters most to you.

Two small pieces of code you own: what the person must see, and how strong the approval must be.

What the person sees in your appExample
OmniArx checks the request
Only the approved request runs

Anything different is refused before it reaches your API.

Where a yes has to be proven.

An action is two small pieces of code you write and own. One says what the person must see. The other says how strong the approval must be.

Refund above a limitNeeds approval
$2,400.00
Order
#88213
To
Card ending 0917
Refused if the amount or card changes
Shipping-address changeNeeds approval
New address
Order
#88213
Ship to
12 Harbour Road
Refused if a different address is sent
Payout to a new beneficiaryNeeds approval
$9,800.00
Beneficiary
Never paid before
Account
Ending 3310
Refused if the beneficiary changes
Credit limit increaseNeeds approval
$12,000
Current limit
$5,000
Customer
Card holder
Refused if the new limit is higher

How it works.

01

Describe the screen

Describe what the person must see. You write the code that turns the request into the fields shown on the phone.

02

Set the strength

Set how strong the approval must be for that route. A route that sets no level will not start.

03

Point the route

Point the route at OmniArx. The check verifies each request and forwards it to your API unchanged.

Measured for your action.

Need measured results for your own action? That is what a pilot produces. We measure it on your own system. A pilot runs on one of your routes and ends with a live evidence session on your own results.

  • A shipping-address change is the retail version of a redirected wire. It deserves the same proof.
  • You own the code that decides what the person sees and how strong the approval must be.
  • Your API is not modified.

Bring the action
you want to protect.

Tell us what your agent does and which system it calls. We will map the route, the approval screen and where the check goes.

Book a session