Earlier versions
Last updated
Last updated
We introduced the possibility to handle KYC processes without the integration with 3rd party service Shufti Pro and without the necessity to collect any info in the portal. Now admins can set "manual" KYC provider and handle KYC checks by any mean they prefer out of the portal. Read more how to set and handle manual KYC checks in KYC checks and
As usual, with this version we've brought some UI improvements and couple of bug fixes. Apart from that, we introduced one feature for end users and made some significant changes in the configuration flow and WLP management.
End users can benefit from the possibility to define amount to pay or amount to receive as a payout within Redemption flow. WLP calculates all the fees and includes them automatically based on the redemption method parameters.
With this version WLP admins can try following improvements:
When new setting "Use WLP direct links for redemption and purchase" is switched on, direct links to specific featured asset or specific redemption method can be used by end users. When they open portal by clicking this direct link, user will be able to see and start the flow only for that featured asset or redemption method which was specified in the link. Read more about this functionality here
We've calculated all the values based on conversion rate, but we recommend to check current minAmountNet and maxAmountNet values anyway. Check detailed information about redemption configuration updates here
Though, please, keep in mind that some of the asset properties for purchase and redemption features must be still configured in the json config file under Advanced management. Also, we are not asking you to replace the existing configuration of the existing assets used in WLP. We've moved all the properties from the config file to the WLP and saved it. But if you decide to change some of these properties, you should amend existing asset in the WLM and define all the WLP properties. For all new assets added to WLP, please, use new approach for asset definition described in Asset configuration
Please, use the square picture of file type PNG; recommended size: 400*400 px.
You won't see any difference unless you try to save updated config file without some mandatory values under Advanced config management.
For the future, please, don't modify the structure of the config file. Only reuse existing objects.
You shouldn't care about differences between assetId and ledgerId anymore. Just use uniqueAssetId which is available in the Asset details page in WLM
With this version WLP admins can try following improvements:
now portal available languages and its currency can be adjusted with the help of UI instead of json config file. Check the updates under Tenant configuration
colors management became much more easier - now admin should define only 10 colors for different groups of UI elements described in the colors.json file which can be found in the Azure blob storage. Check the updates under Branding management
exported data from orders and redemptions lists now contain all available data in the portal
In this version we focused on redemption process refurbishment. We introduced following changes:
now end-users will start receiving redemption details to their emails when redemption request is created
some refurbishments in the steps of redemption request creation flow to make it more user-friendly
Also we fixed some bugs and introduced some architectural changes to make our solution more stable and to improve user experience.
In this version we refurbished the order creation process to improve UX and introduced shopping cart edge cases processing to make sure you don't face any issues. Additionally we made purchase reference code available for all orders (it was available only for bank transfers till this version) and updated our recommendations how to define its template to make sure you will have around 11 mln unique codes. Now you can use it to support communication between you and your end users.
Also now admins can provide additional data necessary for your business cases for each order and redemption in order details and redemption details correspondingly.
Please, note: we renamed menu entries! Now navigation should be easier for you and your end users.
Also we fixed some bugs and introduced some design and architecture changes to improve user experience.
Starting from this version admins can manage features available in the portal, list of admins of the portal and configure WLA name used with WLP using UI instead of configuration management file. We will keep replacing configuration management file entries by UI in the upcoming versions.
And as usual we fixed some bugs and introduced some design and architecture changes to improve user experience.
In this version we introduced possibility to switch languages which means that admins can set the list of available languages for portal (find how to configure them in Tenant configuration) and users can easily select desired language among English, German, Spanish.
Starting from this version admins can define the list of bank identifiers they need for their bank transfers including adding specific local ids and intermediary bank details (find how to configure them in Features configuration). Also now admins can check the invoice details and order details which were sent to the end user when order was placed in purchase details (purchase management view).
Also we fixed some bugs and introduced some design changes to improve user experience.
In this version we introduced some changes in purchasing process: Users can give crypto wallets names when saving them. Users can see and manage them in account details
Admins can provide different custom HTMLs for logged in and non-logged in users for featured asset for purchasing (check Features configuration)
User can see how much time is left for finishing order and how long portal owner will wait for bank transfer payment
Also we fixed some bugs to make our solution more stable and improved UX.
In this version we made some changes in existing functionality, introduced some new features and fixed some bugs to improve UX and make solution more stable
Imprint: Impressum/contact information can be provided by admin Imprint section can be fully customized via a custom html
Displaying the numbers with decimal and thousand separators based on the tenant language for English, German and Russian language. Spanish is still in our backlog.
Now users can see when they were not approved by admin yet
Now it is possible to use decimals in the desired amount to redeem
users are not forced to fill birthdate and nationality to complete the purchase. Also they won't see this data in bank accounts
payment method "Bitcoin" was renamed to "Cryptocurrencies" because Coinify, with which our solution is integrated, provides a wide range of cryptocurrencies
New mode for secondary markets is introduced in the Tenant WLP configuration under Configuration management
Due to the changes in the redemption flow for end users we removed "feesOnTop" configuration of redemption methods and moved minimum and maximum amount of asset to redeem to the "user pays" configuration section
Most of the asset configuration can be done with WLM
Starting from this version most of the general asset configuration necessary for WLP can be defined with the help of WLM UI when asset is being setup by the admin. Admins should add these properties as additional ones from the collection "WLA&WLP configuration". We've already prepared everything, just add this folder, fill the values of WLP properties and remove unnecessary ones. Check how to do it in .
We have new recommendation for asset and redemption pictures
We've enriched validation rules for Advanced config management to make sure that you don't miss any important configuration parameters.
Now WLP uses unique asset id in the configuration under Advanced config management
This version brings significant changes for the end users too. We improved UX of the redemption request creation process including the flow for using saved bank accounts and crypto wallets. Check the updates under
all redemption requests are created with the redemption reference code. Admins are responsible for managing redemption reference code templates in configuration management, this is the same reference code template which is used for purchases, don't forget to adjust it to your needs as described here
In this version we introduced integration with KYC provider Shufti Pro to let admins define necessary KYC tiers and functionality available for them. Check how to configure KYC functionality. Your end-users will have to go through KYC checks to get access to the functionality according to defined tiers as described in and your admins will have to take care of approval of KYC tier upgrade requests as described in .
Also now you can configure disclaimer text for using New Ethereum wallet as a collection method. Check
