Community concept illustration—not an actual app screen.
An account screen can contain several long strings of characters. Some identify a bank account, some identify a routing rail, and some identify a crypto address. They are not interchangeable just because they all look technical.
A virtual account is useful only when the sender uses the correct payment instructions. Start by identifying what kind of payment the details are intended to receive.
Understand what the account details do
Jupiter’s remittance documentation describes USD and EUR virtual accounts after verification, with EUR availability dependent on residence. Incoming fiat received through those accounts funds Spend. Crypto is deposited through the separate crypto-deposit flow, not directly into virtual bank details. Virtual accounts explained
Do not present the existence of bank-style details as evidence that you have opened a conventional bank account with every protection or feature you expect from one. Review the provider and partner terms for your specific service. Partner risks
Match the instructions to the sending bank
Read the currency, account holder, account identifiers, routing information, payment reference if required, and the rail specified by the receiving service. Ask the sending bank to confirm that it can make that exact kind of transfer.
A list of currency symbols in an app is not permission to send any currency using any international wire option. When the receiving instructions and the bank form do not clearly match, pause and ask official support rather than improvising a field.
Pay special attention to EUR
The current remittance documentation specifies SEPA for EUR remittances and warns that EUR SWIFT transfers are not supported. This is a good example of why matching the currency alone is insufficient. EUR rail limitation
If your bank offers several options, do not select one because it sounds faster. Confirm that the recipient account accepts it and inspect its fee. A familiar bank brand does not remove the need to match payment rails.
Read both sides of the funding cost
Your bank may charge for sending, and the receiving virtual-account rail may have its own fee. Jupiter’s detailed schedule lists bank pay-in charges separately from payout charges. Funding fee schedule
When calculating your usable balance, distinguish the amount you instruct the bank to send from the amount expected to credit Spend. Do not assume they are the same. Check the receiving instructions before using a tiny test amount, especially where a fixed fee could consume it.
Keep business and personal assumptions separate
Do not promise clients, employers, or customers that these details accept every type of incoming payment until you have checked the account’s actual permitted uses. Account-name requirements, payment-purpose questions, and document requests should be resolved through the provider rather than a community article.
Likewise, a successful personal transfer does not prove that a larger or differently sourced transfer will be handled the same way. Keep records and comply with the information requests for the transaction you are actually making.
Track the result in the correct balance
After the bank releases the transfer, keep its receipt and reference. Wait for the receiving account to credit the expected balance. A bank saying “sent” and Spend saying “available” are two different checkpoints.
If the transfer does not appear, compare the submitted details with the original receiving instructions and use official support with the reference. Do not make another payment simply to see whether it works. It is better to understand the first transfer than to create two unresolved ones.
A simple final check
Before sending, finish this sentence: “I am making a bank transfer in this currency, over this rail, to these verified bank details.” If the sentence instead mentions a token or blockchain address, you are in a different funding flow and should use the corresponding guide.
Sources & what was checked
Public documentation reviewed 23 September 2026. This is a documentation-based guide, not a first-hand account, identity-verification or payment test. Open the current sources before acting.
