Skip to main content

Wallet Currency Parameter Changes

Version 1.3 introduces some changes to the walletCurrency passed when integrating with Elements:

walletCurrency now works app-wide​

Before the change, in order to use walletCurrency, Partner Account Manager of VONQ should have enabled End User payments on our admin panel.


We enable all payment methods on our Sandbox environment by default for development purposes. The ATS Developer at early stages of development, did not pass a walletCurrency which defaulted to USD then a wallet has been created for the user.


This lead to some issues:

Wallets created in a currency needs to be manually changed by VONQ​

When ATS Developer advanced in the HAPI Elements integration and decided to pass a different walletCurrency than the default USD; existing users, who already had a wallet created, got stuck on that currency and led to VONQ doing adjustments on our admin panels so that a new wallet can be created with the new walletCurrency.


If the ATS wants to use End User Payments, the problem mentioned still remains. When you want to use a different currency than USD, your users (identified by clientId passed during integration) who has had a wallet created with the default currency of USD will need adjustments; talk with your Partner Account Manager to get this resolved.

note

Please note that, before going to production, the payment methods must be set and not changed later; if you decide to use wallets in production, then you decide to NOT use wallets and ask us to disable it, it is currently not possible to shift Wallet Balance or any money to user's account.


In this case, because we cannot disable a payment enabled in production, you need to manually hide the payment method as described in Payment Methods Configuration recipe.

walletCurrency being respected app-wide​

When ATS management decided that they only want the ATS Payments, but at the same time, they want HAPI Elements to show prices in a different currency than USD, user received an error HAPI Elements received "walletCurrency" query parameter on "loader.js" but wallet payments are not enabled by VONQ for your ATS. Please contact your Partner Account Manager if you want to use wallet payments..


This restriction has been removed and error won't be visible anymore. It now makes sense to actually rename walletCurrency to currency as it is now app-wide however to preserve backwards compatability, name of walletCurrency is NOT changed to currency and also not to overcomplicate it further: currency parameter is NOT added as a new parameter when loading HAPI Elements; in other words we keep using walletCurrency as if it was named just currency because it works like an app-wide currency now.