Designed with payment-data boundaries in mind.
Payment Bridge is built to reduce manual entry errors — never to bypass payment controls. Card data stays on your terminal hardware. Sensitive actions are guarded. Roles keep your shop’s workflows separate.
What we do — and what we never do
Card data stays on the terminal
All payment processing happens on your terminal hardware and the terminal provider’s secure network. Card data does not flow through Payment Bridge servers.
We don’t store sensitive card data
No full card numbers, no CVV, no expiration dates.
Sensitive actions are guarded
Write-backs to your POS are controlled with merchant safeguards so charges and approved details stay deliberate.
Role-based access
Sub-users for team with a 6-digit PIN for shared workstations, keep workflows clean and separate.
Reduces errors, doesn’t bypass controls
The bridge eliminates manual retyping — the most common cause of mismatched references. It is not a tool to bypass POS or payment rules.
Veteran owned & operated
Built with integrity, care, and accountability. We keep response times fast — every message read within 24 hours, usually within hours.
Card data never touches our servers.
Your existing payment processor handles card data — that relationship doesn’t change when you add Payment Bridge. Card data is captured and processed on your payment terminal and your processor’s secure network, not ours.
Payment Bridge relays the payment instruction (amount and reference) and receives the result (approved status, reference ID, auth code). That’s all we handle — and that’s by design.
Read the full privacy policy →Amount and reference — from your POS to your terminal.
Approved status, reference ID, auth code — back to your browser.
Never on our servers. Stays on your terminal and your processor’s network.
You decide who can do what
Sub-users
Add cashier and front-desk users to your Payment Bridge account, each with their own credentials.
Roles
Cashier and front-desk roles separate the things each role should and shouldn’t do.
6-digit PIN
Quick PIN access on shared workstations — no full password every time, but still controlled.
Controlled write-backs
After a charge approves, the result flows back to your POS — only through controls you set up, never behind your back.
Straight answers, no security theatre
Does Payment Bridge see my customers’ card numbers?
No. Card data is captured and processed on the terminal and the terminal provider’s secure network. The Payment Bridge extension and backend never receive cardholder data.
Are you PCI compliant?
Your existing PCI compliance stays intact — adding Payment Bridge doesn’t change it. Card data is captured and processed by your existing payment processor on their secure network. Because that data never comes to us, your payment processor’s PCI scope remains where it already was. We handle the instruction and the result, not the card data.
What does Payment Bridge actually store?
Result data (approved status, reference ID, auth code) for reporting in your Payment Bridge account, your business contact info, your sub-users, and small browser preferences like your auto-open setting. No sensitive card data — no full card numbers, no CVV, no expiration dates.
Can the extension write things back to my POS without me knowing?
No. Write-backs go through merchant safeguards. The extension is designed to support your workflow, not run silently in the background.
What happens if a charge does not approve cleanly?
You see the result clearly in the side panel. Today, retries and reinitialization are merchant-controlled, and we have safer retry handling on the roadmap.
Have a security question we didn’t cover?
Email us. We’ll answer in plain English — usually within hours.