Security
Built to protect money and data.
Card numbers never reach GIEP. Every merchant’s data is isolated, every change to money is audited, and you can see every time our support team looks in.
Your data
Protected by design, not by promise.
No card numbers
The checkout uses the processor’s secure card fields. Card numbers never touch GIEP or your servers.
Isolated per merchant
Each merchant’s data is separated at the database itself, so one account can never read another’s.
Write-only secrets
Processor credentials, pixel tokens and webhook secrets are stored as references and never shown back.
Signed events
Processor webhooks are verified before they count; GIEP signs every event it sends you.
Your team
The right access for every person.
Two-factor sign-in
Authenticator apps and backup codes; owners can require it for the whole team.
Roles
Owners, admins, developers and support each see and do only what their role needs.
Audit log
Every change to money, processors, routing, members, keys and settings, append-only.
Secure sessions
HttpOnly cookies; resetting a password signs out every other session.
Our support team
When we help, you see it.
Read-only, time-boxed
A support session needs a written reason, lasts at most 30 minutes and is read-only by default.
Never moves money
Support can never take payments, refund, see credentials, create keys or change your team.
Listed in your account
Your owner is emailed when a session starts, and every session appears in your activity log.
Questions
Questions about security.
Anything else, ask us on a demo call.
No. Shoppers enter card details in the processor’s secure fields; GIEP keeps references, never card numbers.
Ready when your next order is.
See GIEP on your own store and processors. A 30-minute call, no slides.