TripWorks keeps card data with Stripe, its payment processor, and gives every team member their own login and permissions. This page answers the security questions operators ask most often, about sign-in, card data, and access to your account.
In this article
Signing in
- Each team member has their own login. Staff sign in with their email address and password on your account's login page. Invite each person separately rather than sharing a login. See Invite users to your TripWorks account.
- Single sign-on (SSO) isn't available. TripWorks doesn't support signing in through Google, Microsoft, Okta, or another identity provider.
- Passwords can be reset by each team member from the login page. See Reset your password.
Access and accountability
- Permission groups control what each team member can see and do, such as taking refunds or changing setup. See Permission groups.
- The audit log records who changed what and when across your account, so you can review activity by record or by team member. See Use the audit log.
Card data
- Stripe processes every card payment. Online, guests type their card into Stripe's secure payment fields, and in person, card readers encrypt the card inside the reader. Stripe is certified as a PCI Level 1 Service Provider.
- TripWorks never stores full card numbers or security codes. For a saved card, TripWorks keeps only Stripe's reference to it plus the brand, last 4 digits, expiration date, and cardholder name. See Is my card saved when I book online?
- 3D Secure runs automatically when a guest's bank requires it. See Does TripWorks support 3D Secure (SCA)?
Examples
- Answer a vendor security questionnaire. Use this page for sign-in, card data, and access questions, and contact support for anything it doesn't cover.
- Remove a former employee's access. Turn off Can sign in to TripWorks on their team member profile so their login stops working, then review their recent changes in the audit log. See Disable a user's login.
Frequently asked questions
Does TripWorks support single sign-on (SSO)?
No. TripWorks doesn't support SSO through Google, Microsoft, Okta, or any other identity provider. Each team member signs in with their own email address and password, and you control what they can do with permission groups.
Does TripWorks store credit card numbers?
No. Card numbers go straight to Stripe, TripWorks' payment processor. For a saved card, TripWorks keeps only Stripe's reference to it plus the brand, last 4 digits, expiration date, and cardholder name. Security codes are never stored.
Is TripWorks PCI compliant?
Card data is handled by Stripe, which is certified as a PCI Level 1 Service Provider. Guests enter cards into Stripe's secure payment fields online, and TripWorks card readers encrypt the card inside the reader, so full card numbers never reach your TripWorks account.
Can I see who changed something in my account?
Yes. The audit log shows who changed what and when, across your whole account, on a record's History tab, or on a team member's profile. See Use the audit log.
Related
Built for attractions, tours & activities
Payments that just work
See how attractions, tours, and activities take secure card payments on TripWorks. Book a demo and make the switch.