Requirements and Support

Production requirements, CSP, browser support, and operational guidance for rinne-js.

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

Requirements

HTTPS required

Wallet payments do not work on insecure HTTP origins. Serve all checkout pages over https://.

Apple Pay domain verification

Before you enable Apple Pay in production, download the Apple Pay domain association file and host it at /.well-known/apple-developer-merchantid-domain-association on every domain and subdomain where Apple Pay runs, then share the list of domains with Rinne so they can be submitted to Apple. The file is the same for every merchant. See Apple Pay domain verification for details.

Content Security Policy

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;

User requirements

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

Browser	Apple Pay	Google 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.