Storage
Encrypt receiving details before storage
Account numbers, routing numbers, IBANs, SWIFT/BICs, and sort codes are encrypted with AES-256-GCM before they are stored.
Virtual account controls
Keep receiving details protected and every deposit traceable
For enabled virtual-account programs, Gruv encrypts stored bank details, keeps records scoped to the right account, and carries the status and references behind each deposit.
Encrypted bank detailsAccount-scoped recordsTraceable deposit states
Data controlsReceiving record
Record accessAccount-scoped
Stored bank detailsEncrypted
List responseMasked
Create requestReplay-safe
Deposit trace
StatusHeld for review
Provider referenceAttached
Sender account•••• 4821
Status and references stay together
Protect sensitive details without slowing down operations
Give teams the context they need while keeping full bank details behind account-scoped access.
Everyday work
Use masked details in list views
List views use masked account values, so routine work does not need decrypted bank details.
Access
Keep records inside the right account
Authenticated requests carry an account scope, and virtual-account and deposit lookups use that same scope.
Retries
Retry account setup without guesswork
A stable request key lets the same create request be replayed safely and rejects a different request that tries to reuse it.
How it works
Give every deposit a clear, traceable state
More in Virtual Accounts
Explore more in Virtual Accounts
Frequently Asked Questions
Who issues the receiving details and holds the funds?+
The enabled payment provider issues the receiving details and holds funds under its program terms. Gruv keeps the operating record and provider references; Gruv does not issue the account or hold the funds.
Which bank details are encrypted?+
Stored account numbers, routing numbers, IBANs, SWIFT/BICs, and sort codes use AES-256-GCM encryption. Masked account and routing values are stored separately for list views.
What happens when a deposit needs review?+
A configured rule can hold the deposit before credit. Gruv keeps the deposit status and provider references together so your team can follow the case without losing the transaction thread.
Is the same setup available for every account?+
Virtual accounts are enabled per account and provider program. The provider, markets, currencies, receiving structure, screening, and customer access are confirmed during setup.
Next step
See where Gruv fits
Tell us what you are trying to do, where it needs to work, and how your team handles it today.
Contact the team