01
Stripe
Organizations on Stripe take cards through Stripe's Payment Element, an embedded form Stripe serves and controls. Stripe is a PCI DSS Level 1 service provider. Card details travel from the browser to Stripe; Resyrv receives a token.
+ Security & trust
PCI DSS: how card payments stay out of Resyrv's hands
PCI DSS is the card brands' security standard for anyone who takes card payments. The lightest category, SAQ A, is for merchants who have fully outsourced card handling to a compliant processor and never see, store or transmit card data themselves. Resyrv qualifies for it on both processors it supports.
All standardsHow Resyrv meets it
02
Authorize.net
Organizations with their own Authorize.net merchant account take cards through Authorize.net's hosted card window, which opens over the page and is served by Authorize.net. Card details travel from that window to Authorize.net; Resyrv receives a one-time token and charges it.
03
What Resyrv keeps
The card brand and last four digits, for display ("Visa ending 4242"), and the processor's token for saved cards. No full card numbers, expiry dates or security codes exist anywhere in Resyrv.
04
Self-assessment
Resyrv completed its PCI DSS Self-Assessment Questionnaire A on September 18, 2026 and renews it annually.
Questions? Email security@resyrv.com.