Final Say authentication & approval
Final Say is included in the server platform. The Server calls its RP service for FIDO2 login and verification of specific transaction approvals.
IDENTITY & TRANSACTION AUTHORIZATION
Who are you?
What are you
authorizing?
Connect identity, workplace services and approval of the exact action. From the Chrome Roads Server to your enterprise’s card and your customer’s app.
Chrome Roads Server / Chrome Roads Card / Final Say
FROM IDENTITY TO ACTIONInteractive illustration
Your banking appPowered by Final Say
Identity verified 01
REVIEW TRANSFER
$2,500.00
- To
- Acme Supply
- Destination
- Account ending 4821
- From
- Business checking · 1048
Approval tied to these specific details.
FINAL SAY BY CHROME ROADS
Illustrative flow. No real account or transaction is connected.
Identity establishes the person.
Authorization establishes the action.
01Authenticate
the person
the person
02Review
the details
the details
03Verify
the approval
the approval
ONE PLATFORM. CONNECTED POSSIBILITIES.
Software that connects.
Hardware that extends.
The Chrome Roads Server brings together Final Say and a broad range of connected card services. Pair it with the Chrome Roads Card for enterprise operations, or deploy Final Say independently in your customer applications.
01 / CARD OPERATIONS
Chrome Roads Server
Includes Final Say for authentication and approvals, plus card provisioning, location, messaging, access, safety and updates.
Explore the server ↗02 / IN YOUR ENTERPRISEChrome Roads Card
A dedicated device for identity, access and approval, built for enterprise operations.
Meet the card ↗03 / STANDALONE SOFTWAREFinal Say
The mobile SDK and FIDO2 RP service for authentication and transaction approval. Integrate with your app and backend, independently of the Chrome Roads Server.
Explore Final Say ↗CHROME ROADS SERVER
The center of a
connected card platform.
The Chrome Roads Server includes Final Say alongside identity, access, location, communications, safety and card-management services. It calls Final Say’s RP service for authentication and transaction approval. That same service is also available independently with the mobile SDK.
Card & credential management
Provision cards, manage credentials and monitor card health, including battery and device status.
Indoor location services
Bring card location and proximity information into workplace visibility and location-aware workflows.
Text messaging to the card
Deliver individual messages, team broadcasts and operational alerts to the card’s display.
Panic-button alerts
Connect a cardholder’s request for help with the enterprise’s emergency response workflow.
Fall detection
Use card motion sensing to support fall-detection events and workplace safety notifications.
Door & facility access
Support physical access workflows using the card’s MIFARE DESFire credentials and compatible door-access systems.
Over-the-air card updates
Manage delivery of firmware and software updates to Chrome Roads cards throughout their deployment.
Card services work together with the card’s hardware and your facility integrations.
See how the platform connects ↓CHROME ROADS CARD
More than a badge.
Built for your working day.
Who are you? What can you access? What are you authorizing? Bring those decisions together in a dedicated, card-sized device that also keeps your people connected.
MEET THE CHROME ROADS CARD
The idea.
In 60 seconds.
Chris Williams introduces the thinking behind ChromeID: a dedicated identity device connected to a broader software platform.
Watch on YouTube ↗POWERED BY THE CHROME ROADS SERVER
Issued by your enterprise.
Managed throughout its life.
Provision cards, manage credentials, monitor device health and deliver over-the-air updates from the Chrome Roads Server. The card SDK gives your team a foundation for specialized enterprise applications.
Explore the server’s services ↑Put the card to work in your environment.
Discuss a card pilot Hardware development is advancing toward pilot use. Plan the workflows and facility integrations for your deployment.
TWO WAYS TO PUT IT TO WORK
For your people.
For your customers.
A shared platform, with deployment choices for different relationships and environments.
ENTERPRISE OPERATIONS
Dedicated identity.
Purpose-built
for work.
The Chrome Roads card brings a secure element, biometrics and an on-device display together in a dedicated platform for workforce identity and enterprise applications.
- Physical and digital access
- Dedicated approval workflows
- Enterprise messaging and workplace services
Explore the Chrome Roads Card ↑Hardware development is advancing toward pilot use.
Chrome Roads Server+Chrome Roads Card
FINAL SAY / CUSTOMER APPLICATIONS
Your app.
Their phone.
Specific approval.
Embed Final Say’s mobile SDK in your app and integrate its standalone FIDO2 RP service with your backend. Your mobile deployment does not require the Chrome Roads Server or card.
- Transfers and beneficiary changes
- Sensitive account updates
- Customer approval inside your application
Discuss a mobile integration ↗Ask about Android and iOS support for your pilot.
Final Say SDK+Final Say RP service
FINAL SAY BY CHROME ROADS
Final Say.
Your app. Your backend.
Final Say combines a mobile SDK with a standalone FIDO2 relying party (RP) service. Embed the SDK in your app and deploy the RP service within your institution, integrated with your own backend.
Developed from the Chrome Roads platform, Final Say brings authentication and transaction approval to your customer applications. Its RP service is also used by the Chrome Roads Server.
Final Say = mobile SDK + standalone RP service.The full Chrome Roads Server is not required.
See the two integration paths ↓BEYOND THE LOGIN
A person signs in.
A specific action gets approved.
A login alone does not establish approval of an amount, a destination or a permission change. Make the requested action part of the decision.
- 01
Request
Your system submits the specific transaction or sensitive action.
- 02
Review
The person sees the relevant details on their enrolled app or card.
- 03
Verify
Final Say’s RP service checks approval evidence against the requested action.
- 04
Execute
Your integrated backend acts on the authorized request.
Changed terms? New approval.
The integration must connect the verified decision to the same action your system executes.
THE SERVER. THE CARD. FINAL SAY.
One enterprise platform.
A standalone path
for mobile.
The Chrome Roads Server brings the platform’s services together, including Final Say. Connect the Chrome Roads Card for dedicated identity, access, communications and workplace services.
Final Say is also available separately. Embed its mobile SDK in your app and integrate its RP service with your bank’s backend, without purchasing the full Chrome Roads Server.
Talk through your architecture ↗THE ENTERPRISE PLATFORMChrome Roads Server
Includes Final Say + connected card services
Location · Messaging · Safety · Access · Updates
Card connection
Chrome Roads Card
Dedicated identity, access
and workplace services
RP service call
Final Say
FIDO2 authentication
& transaction approval
FINAL SAY / ALSO AVAILABLE SEPARATELYMobile SDK + RP service
Your app + your bank’s backend.
No Chrome Roads Server required.
Conceptual product relationships. Your backend executes approved business actions.
TAKE A CLOSER LOOK
Understand the platform.
Start with the story. Then get into the details of your deployment.
LET’S BUILD THE RIGHT DEPLOYMENT
Start with the action
you need to protect.
Explore the Chrome Roads Server, a card pilot,
or Final Say for your customer applications.