Skip to main content
Use this checklist before you go live with wallet, card, or 3DS flows.

​
Requirements

Wallet payments do not work on insecure HTTP origins. Serve all checkout pages over https://.
Work with Rinne support to complete Apple Pay domain verification before you enable Apple Pay in production.
If your application uses CSP headers, allow these origins:
script-src https://js.evervault.com;
connect-src https://keys.evervault.com https://api.evervault.com https://api.rinne.com.br https://api-sandbox.rinne.com.br;
frame-src https://ui-components.evervault.com;
For a successful checkout, users need:
  • A supported browser and device
  • A configured wallet with at least one eligible card
Keep API keys server-side and process encrypted payloads from frontend elements on your backend.

​
Browser support

BrowserApple PayGoogle Pay
Safari (iOS 10+, macOS 10.12+)✅✅
Chrome✅✅
Firefox❌✅
Edge✅✅
Wallet availability also depends on device capabilities and wallet setup. Apple Pay requires Safari configuration, and Google Pay requires at least one registered card.