Payers need clear receiving instructions
A payer needs clear receiving instructions tied to the correct business and account record.
Global
Receiving details with a traceable deposit record
Request receiving details, share the returned instructions, and follow virtual-account and deposit status with references and timestamps.
Receiving-detail requestVirtual-account statusDeposit references
Your virtual accountsActive regions · expandable coverage
🇺🇸USDUS
ACH · Wire
🇪🇺EURDE
SEPA
🇬🇧GBPUK
Faster
🇯🇵JPYJP
Zengin
🇦🇺AUDAU
NPP
🇨🇦CADCA
EFT
🇸🇬SGDSG
FAST
🇭🇰HKDHK
FPS
🇲🇽MXNMX
SPEI
🇪🇺Active
Euro · Germany
SEPA · SEPA Instant
Account name
Acme Technologies GmbH
IBAN
DE89 3704 0044 0532 0130 00
BIC
COBADEFFXXX
Reference
ACME-24-Q4
Where international receiving stalls
Receiving-detail status is easy to lose
Without the request and virtual-account state in one place, ops cannot tell whether details are requested, active, or suspended.
Deposits land unattributed
A deposit needs its virtual-account reference, provider transaction reference, amount, status, and timestamps before ops can investigate it.
Returns need an investigation trail
When a deposit is held or returned, support needs the current status, reason, reference, and event timeline on the record.
Receiving Ops
Receiving details with deposit history
Request receiving details, then keep virtual-account status and deposit references, states, and timestamps together.
Receiving-detail request
Submit the account, currency, profile, and request reference. Availability is confirmed during setup.
Virtual-account status
Read the current virtual-account state and the receiving details returned for the account.
Deposit list and detail
List deposits for a virtual account and open the detail record for amount, status, references, and timestamps.
Returns with clear status
A held or returned deposit retains its current state, available reason, references, and event timestamps for investigation.
Shareable receiving instructions
Share the receiving instructions returned for the active virtual-account record.
Operations references
Keep the virtual-account ID, provider transaction reference, status, amount, and timestamps available for ops review.
Capabilities
What receiving teams need next
Request and status
Request receiving details and review the returned virtual-account state.
Receiving details
Show the instructions returned for the active virtual-account record.
Deposit records
List deposits with amount, status, references, and timestamps.
Exception state
Keep held and returned states visible for operations review.
How it works
From receiving details to a traceable deposit record
Where it works
Where global reach matters
Give operations, support, and finance the same receiving instructions and deposit context.
Marketplaces
Program receiving details
Keep the receiving instructions and virtual-account identifier beside the program account record.
- Receiving-detail request
- Virtual-account identifier retained
- Deposit status and references available to ops
Before vs after Gruv
A clearer trail for receiving operations
Receiving operations are easier to investigate when the request, virtual-account state, instructions, and deposit records stay connected.
Dimension
Without Gruv
With Gruv
Request tracking
Receiving-detail requests tracked outside the account record.
Receiving request and virtual-account status kept together.
Account state
No shared view of requested, active, suspended, or closed details.
Current virtual-account state visible to operations.
Deposit investigation
Deposit status and references must be reconstructed across separate systems.
Deposit detail includes the virtual-account and provider references used for investigation.
Finance follow-up
Finance receives an amount without the status and reference trail.
Per-deposit status, references, amounts, and timestamps remain available to operations.
More in Virtual Accounts
Explore more in Virtual Accounts
Frequently Asked Questions
Which deposit details can operations review?+
The deposit record can expose its amount, current status, virtual-account reference, provider transaction reference, and relevant timestamps.
How do we know whether receiving details are ready?+
Use the current virtual-account state and the receiving instructions returned for the account request.
What happens if a deposit is returned?+
Use the returned status, available reason, references, and event timestamps to investigate the deposit record.
What can we share with a payer?+
Share only the receiving instructions returned for an active virtual-account record.
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