Security and payment processing principles
RoyaleDirect approaches security as an operating discipline: layered authentication, encryption in transit and at rest where designed, continuous monitoring, and payment processing controls aligned with institutional banking practice and client-protection processes.
1. Identity, sessions, and OTP
Access begins with something you know (password or passkey where enabled) and something you have (device-bound OTP, authenticator app, or SMS/voice OTP where still permitted). Privileged actions—new payees, large transfers, card unfreeze, profile changes—re-challenge with step-up OTP.
One-time passwords
- OTPs are time-bound and single-use. Reuse of a code is rejected.
- Server-side validation records attempt counts; repeated failures temporarily lock the step-up challenge.
- Delivery channel preference can be constrained by risk score (for example, authenticator preferred over SMS on elevated risk).
- Staff will never ask you to read back a full OTP on an unsolicited call. Treat such requests as social engineering.
Session hygiene
Sessions expire after inactivity and absolute lifetime limits. Concurrent session policies may terminate older devices when risk signals appear. You can review and revoke sessions from security settings after login.
Device binding
Recognized devices reduce friction but do not remove step-up for sensitive operations. New devices trigger notifications to your registered channels.
2. Encryption and data protection design
Transport security uses modern TLS for public clients. Administrative and service-to-service channels follow internal encryption standards. Sensitive fields are minimized in logs; secrets are stored using industry-appropriate hashing or envelope encryption patterns.
- Passwords are hashed with modern algorithms and never stored in recoverable form.
- Card PANs, where processed, follow tokenization and PCI-aligned handling via designated environments.
- Backups inherit encryption controls consistent with production classifications.
- Key management separates duties between operators where feasible.
3. Monitoring, detection, and response
Monitoring covers authentication anomalies, payment velocity, beneficiary change patterns, geolocation impossibilities, and malware-tainted client signals where detectable. Alerts feed analyst queues under client protection processes.
What you may experience
- Temporary holds on outgoing payments pending confirmation.
- Requests for additional invoices or source-of-funds evidence.
- Forced password reset after credible credential stuffing indicators.
- Card automatic freeze after unlikely merchant patterns.
Incident response principles
Containment first (sessions, cards, rails), then investigation, then client communication through verified channels. Public status notes appear when incidents have broad impact. We do not discuss exploit details that would aid attackers.
4. Payment processing principles
Payment processing is treated as a controlled pipeline—not a firehose. Each stage has a purpose: intent capture, validation, screening, routing, reconciliation, and exception handling.
4.1 Intent capture
You create a payment instruction with amount, currency, rail, and beneficiary. The interface displays fees, FX indications, and cut-off guidance before confirmation. Confirmation binds your intent under the agreement terms.
4.2 Validation
Format checks (IBAN checksums, BIC presence, domestic account schemas), limit checks, balance reservation, and mandate or dual-approval rules for business users run before release.
4.3 Screening
Sanctions, PEP-adjacent signals where applicable, adverse media triggers in enhanced cases, and internal watchlists may delay release. Screening is not optional and is part of institutional banking practice.
4.4 Routing
Domestic, SEPA, or SWIFT paths are selected based on corridor enablement. Intermediary banks on SWIFT paths are outside RoyaleDirect’s direct control; their fees and delays can apply.
4.5 Settlement and reconciliation
Expected value dates are estimates. Returns, recalls, and investigations follow scheme rules. Statements and ledger entries remain the client-visible source of truth once posted.
4.6 Exception handling
Failures produce codes and human-readable reasons where available. Repair fees may apply when beneficiary data was incorrect. Fraud claims require prompt notice and cooperation with information requests.
5. Fraud awareness for clients
- Verify URLs and bookmarks; prefer typing the known domain.
- Ignore unsolicited links claiming “urgent account suspension.”
- Enable alerts for logins, payee changes, and card authorizations.
- Use unique passwords and a password manager.
- When traveling, set geographic card controls deliberately.
- Report suspected compromise immediately via Help or contact channels listed on this site.
6. Business and private banking elevations
Companies should enforce maker-checker, minimize shared credentials, and review user access quarterly. Private banking clients receive clearer escalation paths but remain subject to the same technical controls and screening outcomes.
7. Third parties and processors
Card schemes, messaging networks, cloud infrastructure, and identity vendors participate in the stack. Contractual and technical controls bind processors; however, end-to-end outcomes also depend on merchant acquirers and correspondent banks outside our perimeter.
Frequently asked questions
Do you use SMS OTP forever?
Channel strategy evolves. Authenticator apps or passkeys may be required for higher-risk profiles.
Is biometric login safe?
Device biometrics unlock keys on your device; they are not uploaded as raw biometric templates to RoyaleDirect in standard designs.
Why was my payment delayed?
Validation, screening, cut-offs, or correspondent issues. Check notifications and Help for document requests.
Can staff see my password?
No. Passwords are not recoverable by support.
How do I report phishing?
Forward details via Help or contact email; freeze cards if you interacted with a suspicious site.
Do you offer hardware keys?
Support for FIDO2/WebAuthn factors may be available on eligible packages; see in-app security settings.
Are APIs rate-limited?
Yes, where APIs exist—for abuse prevention and stability.
What is the cold storage story for cash?
Client funds handling follows operational segregation and reconciliation procedures described in agreements—not cryptocurrency cold wallets.
How long are security logs kept?
Retention follows policy and legal requirements; see Privacy for personal data aspects.
Can I whitelist IPs?
Business packages may offer IP allowlists for admin portals.
What if I lose my authenticator?
Use documented recovery codes or identity re-verification. Store recovery codes offline.
Does 3-D Secure always appear?
Only when merchants and schemes invoke it; controls still apply on our side.
Bank with deliberate controls
Open an account, enable strong authentication, and review security settings on first login.
Open account Contact security support