Skip to main content

User Currencies

It is possible for users (including card assignees) to view the balance of a debit-mode card or set spend limits in a secondary currency, different from the card's assigned currency, known as the userCurrency.

What is userCurrency?​

Consider a UK-based company with employees in Sweden. If the company enables SEK as a userCurrency, it can assign this currency when creating cards for Swedish employees. Card assignees will be able to view their card balance and spend limits in their designated userCurrency, providing greater flexibility and transparency in managing expenses.

note

Specifying a userCurrency does not change the underlying card’s issuing currency with our banking partners. The card’s statements will still be reported in the original card currency. Additionally, once a card is created, its userCurrency cannot be changed.

info

This feature is not available on prepaid-mode cards.

Enabling the userCurrency Feature​

This feature is optional. To enable it, contact your account manager or support team with the following details:

  • The name of the application/s you wish to enable the feature for
  • The card profile/s (if not all) you wish to enable it on

You can choose to enable all supported currencies or a subset for each card profile. Supported userCurrency values:

JPY, BGN, CZK, DKK, HUF, PLN, RON, SEK, CHF, ISK, NOK, TRY, AUD, BRL, CAD, CNY, HKD, IDR, ILS, INR, KRW, MXN, MYR, NZD, PHP, SGD, THB, ZAR

Weavr supports USD, EUR, and GBP as currencies for cards. If you choose USD as the base currency, for example, you can also set EUR and/or GBP as user currencies.

Creating a Card with a userCurrency​

To create a new debit-mode card with a userCurrency, use:

POST/managed_cardsTry it

Include the optional userCurrency parameter in the request body, selecting a value from the supported list.

If omitted, spend limits will default to the card’s currency, which also matches the parentManagedAccountId currency, the card's base currency.

The userCurrency setting does not alter the issuing currency or how statements are reported.

note

Once a card is created, the userCurrency cannot be changed.

Retrieving Available-to-Spend Amount​

To retrieve the available-to-spend amount, use:

GET/managed_cards/{id}Try it

or

GET/managed_cardsTry it

If a userCurrency is assigned, the returned amount will be shown in that currency. Otherwise, the amount will be shown in the card’s base currency.

Setting Spend Limits​

To define a spend limit, use:

POST/managed_cards/{id}/spend_rulesTry it

Provide both the currency and amount in the spendLimit object.

If a userCurrency is assigned, spendLimit.value.currency must match it. Otherwise, it must match the parentManagedAccountId currency.

note

minTransactionAmount and maxTransactionAmount are always in the parentManagedAccountId currency, regardless of whether a userCurrency is assigned.

The same logic applies when updating spend rules via:

PATCH/managed_cards/{id}/spend_rulesTry it

Retrieving the Card Statement​

To retrieve a card statement, use:

GET/managed_cards/{id}/statementTry it

If the card has a userCurrency assigned, the response includes a userTransactionAmount field with:

  • userTransactionAmount.currency: the assigned userCurrency
  • userTransactionAmount.amount: the transaction amount in userCurrency
  • userTransactionAmount.userExchangeRate: the conversion rate used, which is the daily ECB rate.
note

If userCurrency equals the original transaction currency, no conversion is applied.

Webhooks​

Authorisation and settlement webhooks for cards with a userCurrency will include:

  • userTransactionAmount: transaction amount in the userCurrency
  • currency: the userCurrency
  • amount: transaction amount in the userCurrency