--- language: "en" --- # Help Center ## Help Center Welcome to the Crassula Help Center, your go-to resource for swift solutions, product insights, and administrative guidance. ### Release Notes * #### [Crassula Release Week 36](https://help.crassula.io/knowledge/crassula-release-week-36.md) September 04, 2026 * #### [Crassula Release Week 35](https://help.crassula.io/knowledge/crassula-release-week-35.md) August 28, 2026 * #### [Crassula Release Week 34](https://help.crassula.io/knowledge/crassula-release-week-34.md) August 21, 2026 ### Documentation * #### [Getting Started Guide](https://help.crassula.io/knowledge/getting-started-guide.md) Welcome to Crassula, a modular, white-label platform for launching fintech products, including neobanks, crypto banking, card issuing, and compliance solutions... * #### [Product Overview](https://help.crassula.io/knowledge/product-overview.md) The Product Overview section introduces the main modules of the Crassula platform. It helps you understand how each product works at a high level and identifie... * #### [System Administration](https://help.crassula.io/knowledge/system-administration.md) Understand how Crassula works behind the scenes. This section covers user interfaces, payments, card issuing, currency exchange, crypto, verification, authoriz... * #### [Release Information](https://help.crassula.io/knowledge/release-information.md) Stay up to date with platform changes: The Release Information section is your reference for planning upgrades, understanding new features, and participating i... --- language: "en" --- # \[2021\] Crassula Release Week 32 *v21.08.1 - 21.08.3* ![release_notes.png](https://help.crassula.io/__attachments/a_13e23a65689ba860426ec06d983043341b72724026fb0fac6bad672190e91bb6/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## New Features ### Crypto wallets Now, any beneficiary walletaddress is masked when demonstrated in the *History* tab. It is possible to copy the whole wallet address by pointing the mouse cursor over the mask and clicking *Copy* . For more information on the payment history, see [Banking Web Interface](https://help.crassula.io/knowledge/banking-web-interface-persons.md). #### Top-up Now the *Top up with another account* option is also available for Card accounts. For more information on the top-up process, see [Banking Web Interface](https://help.crassula.io/knowledge/banking-web-interface-persons.md). *** ** * ** *** ### Improvements #### Account statement PDF account statements are fixed. Now there is no influence on the balance details --- both PDF and XLS statement types provide correct information. #### Card status verification Automatic status verification for cards issued by Intercash is improved. Now the automated functionality is more sustainable. #### Crassula infrastructure update Crassula has updated to PHP 8. The new major update brings new optimization features to the Crassula Software and provides new instruments to make the system even more reliable and efficient. No action is required from the client side. #### eCom transactions Final status verification for eCom transactions is optimized. Now all transactions in the Authenticate status are processed smoothly. --- language: "en" --- # \[2021\] Crassula Release Week 33 *v21.08.4 - 21.08.6* ![release_notes.png](https://help.crassula.io/__attachments/a_d97eadf8347b01bc94d6975b8f09f1464f28c9b644068344f32897af1c083c83/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## Improvements ### Account statements The XLS Account statements of the Web Interface have been adjusted to PHP 8. Now the reports can be downloaded successfully. #### Card issuing limitations The functionality of the card-issuing limitation per client is updated. If the number of cards per client is limited and a client is trying to issue an extra card exceeding the configured limit, the Order new card button will not be available. The limitation can be configured by a Feature change request if allowed by the corresponding service provider. For additional information on card issuing limits, contact your manager. For additional information on the user interface, see [Banking Web Interface](https://help.crassula.io/knowledge/banking-web-interface-persons.md) and [Banking Mobile Interface](https://help.crassula.io/knowledge/banking-mobile-interface.md). #### eCommerce Transactions * The Fraud monitoring mode has been adjusted to PHP 8. Now the report is loaded successfully. * The date filtering has been adjusted to PHP 8. Now the exported list of transactions provides the dates set in the filter. #### Fees check report Now the Fees check report of eCommerce is improved to include only *Active* transactions. Therefore, there is no need to filter out *Active*transactions manually. #### Issued cards provider config The section is deprecated and removed from the Administrative Panel. #### Payouts The *Payouts*section of eCommerce is improved to be loaded faster. --- language: "en" --- # \[2021\] Crassula Release Week 34 *v21.08.7 - 21.08.9* ![release_notes.png](https://help.crassula.io/__attachments/a_baf633048bbf8da1b07c5fa1406285025f4b6ad609ee612d8a679d2160ad79f1/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## New Features ### API for limits Now it is possible to add or delete a payment limit using API methods and check whether one is assigned to a profile, The new feature allows to manage limits for each client when the account is created via API. Contact your manager for additional details on the API methods available. #### Dormant account flag The new filtering option is implemented in the Administrative Panel. Now it is possible to filter out accounts that have had no financial activity for a defined period of time. The time period after which the account is considered dormant can be set in the system configs. For additional information on the filtering option, see [Accounts](https://help.crassula.io/knowledge/accounts.md). #### Pay again functionality The new feature is implemented in the Banking Web Interface and allows users to repeat an outgoing transfer without creating a template. Now the *Pay again* button is available in the outgoing payment details. The feature can be configured by a Feature change request. For additional information on the functionality, see the *Payments and transfers* section in [Banking Web Interface](https://help.crassula.io/knowledge/banking-web-interface-persons.md). #### Pay back functionality The new feature is implemented in the Banking Web Interface and allows users to create a "response" payment to an incoming transfer. Now the *Pay back* button is available in the incoming payment details. The feature can be configured by a Feature change request. For additional information on the functionality, see the *Payments and transfers* section in [Banking Web Interface](https://help.crassula.io/knowledge/banking-web-interface-persons.md). *** ** * ** *** ### Improvements #### Cards delivery Now it is possible to initiate cards delivery in batches once a day when shipping cards to a White label's office. The functionality can be turned on/off in the system configs. When the daily shipping is turned off, each card is delivered separately. #### Compliance workflow The integration with the Payall financial monitoring service is updated to interact with the Railsbank banking provider. Now transaction status is transferred from Railsbank to Payall to synchronize statuses. #### Crypto exchange requests Additional checks are implemented to prevent duplicated crypto exchange requests in the Banking Web Interface. #### Date format The date format in the Administrative Panel is changed from "Sun, 15 Aug 2021 09:39:27 +0000" to "01.07.2021 08:13:41". #### eCommerce limits The *Limits* functionality is deprecated for eCommerce. All the related functions are implemented in the *Anti-fraud* system. #### Minimum exchange amounts Now the *Amount*field is prefilled with the minimum exchange amounts when exchanging currencies in the Web Interfaces. The amount is prefilled only for fiat currencies when exchanging fiat for crypto. The minimum values are set in the system configs. #### Scripts memory usage Now the memory consumption of callback scripts in eCommerce is reduced. The improvement will also have a positive effect on the functionality of receiving callbacks for merchants. *** ** * ** *** ### Fixes #### Merchant card authentication An Error 500 occurred if a merchant entered wrong card details when trying to pass authentication. Now the text message includes additional information --- "Missing merchant data". #### Company profile creation The Owner field did not provide the list of Persons when creating a Company profile in the Administrative Panel. Now the field is fixed and the feature is available. #### Gateway configuration in eCommerce Payment gateway config sections could not be opened via absolute links (for example, when opened from the Transaction details page). The issue is fixed. #### Merchant Web Interface An Error 500 was displayed when the Settings page was opened in the Merchant Web Interface. The issue is fixed and the settings are available. --- language: "en" --- # \[2021\] Crassula Release Week 35 *v21.08.10 - 21.09.1* ![release_notes.png](https://help.crassula.io/__attachments/a_af51c36be503858954c9dbf93a6ab81d5ba15a0688d09df511527f8d1a15fcd0/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## New Features ### API for price lists Now it is possible to check whether a price list is assigned to a profile, add or delete a price category using API methods. The new feature allows to manage price lists for each client when the account is created via API. Contact your manager for additional details on the API methods available. #### Limits check The new *Check* button is implemented for Banking Limits. The feature runs scanning on past transactions for a particular period configured in the limit rules. The transactions exceeding the limit will become *Pending* and the clients will receive a notification. For additional information, see [Limits](https://help.crassula.io/knowledge/limits.md). *** ** * ** *** ### Improvements #### Address field values The error message is improved to provide more details when editing the Address field of a Banking Client. The text is changed from "The value is not valid" to "Only Latin letters, numbers, dots, periods and hyphens are allowed for address line". #### Error messages for payments An Error 500 was displayed if a merchant entered too many symbols into the cardholder parameter when making a payment using API methods. Now the error indicates the rejection reason and provides the "Invalid card holder" message. #### Payment rejection details The *Reason*field is expanded for Sberbank eCommerce provider to indicate payment rejection reasons. Now merchants can see more details on declined transactions. *** ** * ** *** ### Fixes #### Merchant staff An error occurred when trying to create a new merchant staff in the Web Interface. The issue is fixed. #### Payment statements The *Download*button is restored. Now it is possible to download the payment statement in the Banking Web Interface. #### Provider number editing An error occurred when trying to edit the Provider Number parameter in the Banking Administrative Panel. The issue is fixed. --- language: "en" --- # \[2021\] Crassula Release Week 36 *v21.09.2 - 21.09.3* ![release_notes.png](https://help.crassula.io/__attachments/a_8022ede9520cae423e64bc44338fbf859ad388abeeb386c07e7a59f1e759148f/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## New Features ### Payment confirmation checkbox Now transit payments to buy cryptocurrencies can be executed in one step. The new checkbox is implemented to skip the payment confirmation stage and execute the payment immediately. For additional information on payments and transfers, see [Banking Web Interface](https://help.crassula.io/knowledge/banking-web-interface-persons.md). #### Skip transfer pre-approval by default Now it is possible to add a system config to avoid transfer pre-approval for all clients in the system. After the system config is applied, the option remains available for manual change in the Administrative Panel. For additional information on profile configurations, see [Persons](https://help.crassula.io/knowledge/persons.md)and [Companies](https://help.crassula.io/knowledge/companies.md). *** ** * ** *** ### Improvements #### File export Now it is possible to export larger files when downloading transaction lists and reports from the Administrative Panel. The system will prepare large reports and will inform the user with the "Export in progress" message. Once the preparation is done, the download will start automatically. It is recommended to keep the window open. The improvement is applied to all file formats in the following sections: * Banking account transaction list * eCommerce account transaction list * Banking accounting report * eCommerce accounting report *** ** * ** *** ### Fixes #### Action buttons appearance Some action buttons in the Banking Web Interface were not leveled. The issue is fixed. #### eCommerce transactions status Some failed transactions of Sberbank eCommerce provider remained in the Processing status. The issue is fixed. #### Persons list filtering The issue of the non-functioning filter by email is fixed. Now the filter in the Persons list works correctly. #### Transaction status update The *Updated at* parameter of eCommerce transactions was refreshed every time a status request was sent. Now the parameter is updated only when the transaction status is changed. --- language: "en" --- # \[2021\] Crassula Release Week 37 *v21.09.4 - 21.09.5* ![release_notes.png](https://help.crassula.io/__attachments/a_0d3053345c7f4032776dbe32cc6c8752a119907a435c4c76b7c2748f5b83e0e5/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## New Features ### Minimum exchange amounts Now the *Amount*field is prefilled with the minimum exchange amounts when exchanging currencies in the Web Interfaces. The amount is prefilled for all currencies when exchanging cryptocurrencies. The minimum values are set in the system configs. #### XE exchange rates The XE gateway is now available and the exchange rates can be provided. Contact your manager for configuration details. *** ** * ** *** ### Improvements #### Activity logs for Requests Now all activities performed in the Requests section of Exchange are available in the Admin Panel Activity logs. #### Angular 12 implementation Crassula frontend is updated to the new Angular 12 framework. The system update will help us to solve some vulnerability issues in the system. #### Merchant names The *First name* and *Last name* parameters are added to eCommerce reports. *** ** * ** *** ### Fixes #### Country codes for payments An error occurred when executing dynamic payments with both *Beneficiary Country Code* and *Bank Country Code* parameters set. Now the Banking Web Interface provides only the *Bank Country Code* parameter for configuration. #### Payment processing status Some transactions performed by the Yandex service provider could not be processed further. Now the issue is fixed and failed transactions are sent to the *Declined*state. #### Transactions (pre-approval) export An error occurred when exporting transaction lists in the Transactions (pre-approval) section. The issue is fixed. #### Transaction processing status Some transactions performed by the Sberbank service provider were displayed with an incorrect status. the issue is fixed. #### Transactions widget Some eCommerce cryptocurrency transactions were displayed incorrectly in the Merchant Web Interface widgets. The issue is fixed. --- language: "en" --- # \[2021\] Crassula Release Week 38 *v21.09.6 - 21.09.8* ![release_notes.png](https://help.crassula.io/__attachments/a_2269c57e9bc1eb72dce57244c22a67862e2f51cc50da3f87c626b8d2e56d73b9/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## **New Features** ### Card activation configuration Now it is possible to configure the card activation process to be executed only in the Mobile Interface. Thus, if a client tries to activate a plastic or virtual card in the Web Interface, a message defining the restrictions will be shown. This functionality can be enabled in the system settings. Contact your manager for configuration details. #### ClearBank integration ClearBank service provider is integrated to provide multicurrency, virtual, and real accounts. Contact your manager for configuration details. #### Payments return Now it is possible to make recalls and refunds for payments executed by the Bank of Lithuania (Litas) service provider. The functionality can be enabled in the system config and then it will be available in the Administrative Panel. Contact your manager for configuration details. *** ** * ** *** ### **Improvements** #### Issued cards list per account Now it is possible to see all cards issued to an account in the *Account details* tab of the Administrative Panel. #### Multicurrency label The new "Multi"label is implemented for multicurrency accounts to clearly identify them in the Banking Web Interface. Now the currency field demonstrates one of the following options: * If a multicurrency account has only one currency present at the moment, the "Multi" label and the currency code are displayed. * If a multicurrency account has several currencies present at the moment, all present currency codes are displayed. * If there is a mono-currency account, the only currency code will be displayed. *** ** * ** *** ### **Fixes** #### Company documents If company documents were checked by the SumSub service provider, there was a chance they could not be downloaded from the company profile. The issue is fixed. #### Companies list In some cases, it was impossible to scroll the list of companies in the *Profile*option of the Web Interface. The issue could appear if a client had more than three companies present. Now the issue is fixed. #### Prolonged cards Some prolonged cards could fail when making eCommerce payments. Now the expiration dates are rewritten in the system if the validity period was extended by the emitter. --- language: "en" --- # \[2021\] Crassula Release Week 39 *v21.09.9* ![release_notes.png](https://help.crassula.io/__attachments/a_7870e204344af7c8a8361aca441cddf330760255f26a9e21eab49bb53ce9f483/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## **Improvements** ### Compliance workflow The integration with the Payall financial monitoring service is updated. Now additional fields are provided to Payall when performing checks on Companies. The implemented changes make the compliance workflow even more flexible. #### Provider account numbers The provider details field is improved for standard and crypto accounts. Now the Provider field defines which account is primary in the accounts set. For additional information on the account details, see [Accounts](https://help.crassula.io/knowledge/accounts.md). --- language: "en" --- # \[2021\] Crassula Release Week 40 *core v21.10.2, v21.10.3* *client v21.10.1, v21.10.2* ![release_notes.png](https://help.crassula.io/__attachments/a_5246a19d5bc346bb7431d6a9855f481c43bd0a2e68732530a313f742bcb44ca5/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## New Features ### Account country Now it is possible to select a country when creating a banking account in the Web Interface. The parameter influences the list of currencies available for the account. Contact your manager for configuration details. #### New payout parameters New payout request parameters are implemented for the Contact service provider. The new details will be requested to send a payout via the Merchant Dashboard. #### The Italian language Now it is possible to enable the Italian language for the Banking Web Interface. Contact your manager to add the option to your system configurations. *** ** * ** *** ### Improvements #### Payout validation field Now the validation error messages define the parameters that are missing. *** ** * ** *** ### Fixes #### Access roles The *Supervisor View Only* access was not visible for some clients. Now the option is available when configuring access roles for Issued cards. #### API responses The description of some responses was not visible due to the black background. Now the issue is fixed, and the messages are readable. #### Currencies list The list of currencies could be displayed incorrectly in the Web Interface. The issue is fixed. #### Currency exchange In some cases, it was not possible to select an account for currency exchange in the Banking Web Interface. The issue is fixed. #### Transfer details Field mapping for postal codes could not be performed correctly. Now the information is delivered to the corresponding fields. --- language: "en" --- # \[2021\] Crassula Release Week 41 *core v21.10.4, v21.10.5* *client v21.10.3* ![release_notes.png](https://help.crassula.io/__attachments/a_47847bf09db871f4952a24e66543a8b4a4853c109820058ca616771fa5e90787/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## **New Features** ### AlponHub payment components Now all transactions from AplonHub are imported to our system. If the IBAN for the imported transaction is present in the system, then the import will be executed normally. If the IBAN is not present in the system, such transactions will be sent to a special account (specified in the config) in the Pending status. It is possible to manually change the beneficiary of the payment using the newly created button. Contact your manager for configuration details. #### Card PIN display Now it is possible to enable or disable the card PIN display for the Banking Web Interface. The functionality is to be added in the system configs. Contact your manager for configuration details. #### Decta service provider integration Now it is possible to issue cards using the new Decta service provider. Contact your manager for configuration details. *** ** * ** *** ### **Improvements** #### Contact details Now the phone number and email details are displayed as plain text. #### The BGN currency icon Now the BGN currency is provided with an icon in the Banking Web Interface. #### The Italian language icon Now the Italian language option is provided with an icon in the Banking Web Interface settings. #### Payout request parameters Now several new parameters are available for configuration when creating a payout using the Contact service provider. *** ** * ** *** ### **Fixes** #### Banking Web Interface The *Back*button could not operate correctly when trying to issue a card in the Banking Web Interface. The issue is fixed. #### Contact details Emails and phone numbers could not be displayed for some customer profiles when in the *Edit*mode. Now the issue is fixed. #### Multicurrency label The *Multi*label could not be displayed for some multicurrency accounts in the Administrative Panel. The issue is fixed and now all multicurrency accounts are provided with the label. #### Top-up transactions Some failed top-up transactions remained in the Pending status instead of being declined. The issue is fixed. --- language: "en" --- # \[2021\] Crassula Release Week 42 *core v21.10.6* ![release_notes.png](https://help.crassula.io/__attachments/a_48e7c3f43f80cdf52bcc9feffd28251d6db81aee8cf6e4ae871b27f45850f316/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## **New Features** ### Qiwi card acquiring The new card acquiring is implemented. Now it is possible to process eCommerce payments using the Qiwi service provider. Contact your manager for configuration details. *** ** * ** *** ### **Improvements** #### Account service providers The list of service providers is improved to provide more obvious options when editing accounts in the Administrative Panel. Now the Clearbank and Alponhab options are renamed and structured according to countries and currencies. #### Persons The new *Legal name* parameter is implemented for Person profiles. The parameter is set by the Sumsub service provider to avoid errors when processing long names. See [Persons](https://help.crassula.io/knowledge/persons.md)for details. *** ** * ** *** ### **Fixes** #### Payment processing Payment processing could take a long time for some eCommerce clients. The issue is fixed by refactoring the Yandex payments integration. #### Recurring fees Some fees could be debited from closed Primary accounts. The issue is fixed and all fees are charged from active accounts. --- language: "en" --- # \[2021\] Crassula Release Week 43 *core v21.10.7* *client v21.10.4* ![release_notes.png](https://help.crassula.io/__attachments/a_46dd8068de867455945156cb926d04ff823dedfc12e64103344ab56ab7a8c304/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## **New Features** ### Account statement fields Now it is possible to define the fields that are to be displayed in account statements when imported from the Banking Web Interface. The fields are defined in the system configs. #### Converted cards delivery Now it is possible to initiate card delivery in batches once a day when converting Intercash virtual cards to plastic. The functionality is set in the system configs. *** ** * ** *** ### **Improvements** #### Blocked cards Now blocked cards are available in the *Cards* list of the Banking Web Interface. The option can be turned off in the system configs. See [Banking Web Interface](https://help.crassula.io/knowledge/banking-web-interface-persons.md) for details. #### eCommerce payments A new error message is implemented for eCommerce Qiwi Payment Gateway. Now the error message appears if a merchant creates a payment without email details. *** ** * ** *** ### **Fixes** #### eCommerce reports Some massive eCommerce reports could not be downloaded. The issue is fixed. #### LPB payments Some LPB eCommerce payments could not be processed if the *Payment was not found* error appeared. Now such payments are successfully declined. --- language: "en" --- # \[2021\] Crassula Release Week 44 *core v21.11.2* ![release_notes.png](https://help.crassula.io/__attachments/a_a6ff97969ae8e00cba53a8830018d7f63df9452827ef7db741e5974f55aa9916/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## **New Features** ### AliPay acquiring The AliPay acquiring is implemented for eCommerce. Contact your manager for configuration details. #### BIC code field The *BIC code* field is implemented in the Administrative panel for Clear Bank Multicurrency accounts. See [Accounts](https://help.crassula.io/knowledge/accounts.md) for additional details. #### Fees charging Now it is possible to charge fees from a client's account even if the account balance is not enough to cover the charge. Thus, the balance becomes negative and the fee can be successfully charged. The feature can be set in the system configs. #### Transactions import Now Intercash transactions can be automatically imported once a user logs into the Banking Web Interface. The option is set in the system configs. *** ** * ** *** ### **Improvements** #### Batch payments The *Batch payments* page is improved. Now it is possible to see advanced details for each batch payment in the Administrative Panel. See [Batch payments](https://crassula.atlassian.net/wiki/display/HELP/Crypto+batch+payments) for additional information. #### Payout parameters The new *City* and *Recipient address* parameters are implemented for payouts for more than 15000. #### Qiwi payments Now the *Parameter "API key" is not specified* error message provides details on the payment failure. The details are also available in the payment logs. *** ** * ** *** ### **Fixes** #### Column sorting Some columns in Administrative Panel reports could not be sorted. The issue is fixed. #### Crypto transfers Some crypto transfers could be credited twice. Now the issue is fixed. #### Exchange transactions In some cases, exchange transactions could remain in the *Pending* status even if the order was failed. Now the issue is fixed and exchange transactions do not remain in the *Pending*status. #### Price lists In some cases, there were two standard price lists for one category and it was not possible to edit them. Now it is possible to uncheck the *Standard*check box if the issue appears. --- language: "en" --- # \[2021\] Crassula Release Week 45 *core v.21.11.4* ![release_notes.png](https://help.crassula.io/__attachments/a_dacb5045c7d488ea9bf9dc013bac08ee4beec1c2c71b0d2355f14a5857d7bd39/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## **New Features** ### Banking Circle FX The new *Banking Circle FX* service provider is integrated. Now it is possible to receive rates and exchange funds using the service provider. Contact your manager for configuration details. *** ** * ** *** ### **Improvements** #### Access groups Now *Access groups* are divided into *Banking* and *eCommerce*for better usability of the Administrative Panel. #### Decta service provider The *decta_card*filter is added to the list of account transactions in the Banking Administrative Panel. Now it is possible to filter out transactions of the service provider. *** ** * ** *** ### **Fixes** #### Account opening In some cases, it was not possible to open a new account in the Administrative Panel without a service provider defined. Now the issue is fixed. #### Decta account balance Some accounts could not provide balance details in the Banking Web Interface. Now the issue is fixed. #### eCommerce transactions Some filters could not be applied when exporting eCommerce transactions. Now all filters can be applied to the transactions list. #### Insufficient funds error Some exchange orders could be declined due to the *Insufficient balance*error from the Kraken provider. Now the issue is fixed and account balances are processed correctly. #### Railsbank card transactions Some Railsbank card transactions could remain in the *Pending* status even if an error occurred. The issue is fixed. Now all failed transactions are in the *Declined*status. #### The Language section The *Language*section of the Banking Web Interface could not be displayed correctly after language switching. Now the issue is fixed. --- language: "en" --- # \[2021\] Crassula Release Week 46 *core v.21.11.6* ![release_notes.png](https://help.crassula.io/__attachments/a_d152b6f8b36ceeced7fa3e087b0638ca02b753f181765dccda1115dc9b967d88/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## **New Features** ### Antifraud filters for eCommerce Config The following Antifraud filters are implemented in eCommerce Config: * PayerCountryIsInList * PayerCountryIsNotInList * AnyCountryIsInList * AnyCountryIsNotInList #### WeChatPay integration Now WeChatPay is integrated to eCommerce payments for users from China. *** ** * ** *** ### **Improvements** #### Application forms Now the *Application forms* section is removed from Person and Company details. #### Banking Web Interface The MasterCard and Visa logos are updated in the Banking Web Interface. #### Batch payments The Amount minor column is removed from the *Recipients* list of *Batch payments* . The parameter is also omitted from exported files. See [Batch payments](https://crassula.atlassian.net/wiki/display/HELP/Crypto+batch+payments) for additional details. #### Currency exchange The exchange transactions routing is implemented. Now the system checks for accounts of the specified currency when performing currency exchange. If there are no accounts of the specified currency, the system will check for multicurrency accounts. #### Exchange requests Now only a Super Admin can edit exchange request parameters. Other admin roles are only permitted to view the details. #### Issued cards The *Ready to Active* status is renamed to *Ready for activation* . See [Issued cards](https://help.crassula.io/knowledge/issued-cards.md) for additional details on issued cards. *** ** * ** *** ### **Fixes** #### Account details An error occured when editing accounts with no IBAN in the *Account provider number list* section. Now the issue is fixed. #### Card issuing Now the *error 500* text message is displayed correctly defining the issue. #### Crypto transfers In some cases, crypto wallets balance could not be displayed correctly, when performing crypto transfers. The issue is fixed. #### Issued cards list In some cases, it was not possible to open Client profiles from the *Issued cards* section. Now the issue is fixed. #### Issued cards details The *Status check* button was not availble if the provider number was not specified. Now the issue is fixed. #### Virtual cards Some virtual cards required activation. The issue is fixed and virtual cards do not require activation now. --- language: "en" --- # \[2021\] Crassula Release Week 47 *core v.21.11.8-21.11.9* ![release_notes.png](https://help.crassula.io/__attachments/a_2ba15aed1543ada97fe48207eb2cf486c116447b4d9561bce724a2550388b76f/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## **New Features** ### Cashback The new Cashback feature is implemented for outgoing banking transactions of SWIFT, SEPA, and crypto payment methods. See [Price lists](https://help.crassula.io/knowledge/price-lists.md) for additional details. #### ComplyAdvantage integration Now the ComplyAdvantage service provider is integrated to perform transaction monitoring. The process is similar to the one delivered by the Payall compliance system. *** ** * ** *** ### **Improvements** #### Accounts Now Super Admins can edit IBAN details if the account is not provided with an external provider ID. #### Payouts The Contact payouts are improved for eCommerce. Now the Latin alphabet is used when beneficiary name and surname are generated automatically. Thus, payout requests will correspond to localization details. *** ** * ** *** ### **Fixes** #### Transactions Some transactions could be duplicated in the Transactions list. Now the issue is fixed. --- language: "en" --- # \[2021\] Crassula Release Week 48 *core v.21.11.10-21.12.1* ![release_notes.png](https://help.crassula.io/__attachments/a_7bee31b27a9c89733164634838fe89ab71250ccf0ea6d83678bb5a921163b6f2/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## **New Features** ### Amending account currencies Now Super Admins can change currencies of existing accounts in the Administrative Panel. It is not possible to change currencies if accounts are not provided with IBAN. The feature is not available by default, contact your manager for configuration details. #### External fee enabled The new *External fee enabled* parameter is implemented for Banking price lists. If the option is selected, transfer fees will be requested from an external service, while the price list for transfers will be ignored. Contact your manager for configuration details. For additional information, see [Price lists](https://help.crassula.io/knowledge/price-lists.md). #### GlobalPay acquiring The GlobalPay service provider is integrated for eCommerce payments. Contact your manager for configuration details *** ** * ** *** ### **Improvements** #### Account metadata Now account metadata details are moved to the new *Metadata* tab. For additional information, see [Accounts](https://help.crassula.io/knowledge/accounts.md). #### Client cards section The *Client cards* section is renamed to *Saved top-up cards*. For additional information, see . #### Currency icons Now 152 new currencies are provided with a country flag icon in the Banking Web interface. #### Masked CVC Now CVC code is hidden when entering card details in the Banking Web Interface and eCommerce checkout page. *** ** * ** *** ### **Fixes** #### Decta virtual cards Some Decta virtual cards could not be displayed correctly after activation. Now the issue is fixed. #### EURST transactions Now all EURST incoming transactions are displayed correctly and can be received by wallets. #### Kraken exchange In some cases, Kraken exchange orders could have incorrect order types. Now the issue is fixed. --- language: "en" --- # \[2021\] Crassula Release Week 49 *core v.21.12.1-21.12.5* ![release_notes.png](https://help.crassula.io/__attachments/a_755a6dd8687d15c1712a2700df2f56c2bae4611ef2cf03eb9336b6f7c41c3a8c/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## **New Features** ### Cashback configuration Now it is possible to turn off cashback programs in the system configurations. The feature is turned off by default for some service providers. Contact your manager for configuration details. See [Price lists](https://help.crassula.io/knowledge/price-lists.md) for additional details on the feature. #### Editing pending transactions Now Super Admins can edit *Pending* transactions and fees. #### German and Turkish The Turkish and German languages are added to the Banking Web Interface. The new languages are to be added to the system configurations. *** ** * ** *** ### **Improvements** #### Account details Now BIC and Sort codes are displayed for ClearBank accounts in the Banking Web Interface. #### Aplonhub and ClearVirtual accounts Now it is possible to make transfers between virtual accounts of a single client. The new feature expands the functionality of Aplonhub and ClearVirtual service providers. #### Service providers The SwiftClear bank is added to the list of service providers in the Administrative Panel. *** ** * ** *** ### **Fixes** #### Cashback configuration The *Currency* field was not visible for cashback programs with a *Crypto* payment method selected. Now it is possible to select a cryptocurrency for reward programs. #### ClearBank IBANs Some ClearBank IBANs could be duplicated when performing tests in the Administrative Panel. Now the issue is fixed. #### Companies An Error 500 was displayed when opening or editing company details in the Administrative Panel. Now the issue is fixed. #### Crypto accounts For some service providers, it was not possible to reactivate crypto accounts that had been closed by mistake. Now the issue is fixed. #### Deposit functionality In some cases, it was not possible to create a deposit transaction manually via the Administrative Panel. Now the issue is fixed. #### Identification requests An error occurred if an administrator opened the documents sent for verification. Now the *Identification requests* section is working correctly. --- language: "en" --- # \[2021\] Crassula Release Week 50 *core v.21.12.7-21.12.8* ![release_notes.png](https://help.crassula.io/__attachments/a_b951201cac066711d2ce6f82595fcb8d7eeb986489ac15004405ec7729807000/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## **Improvements** ### Sign-Up page Now the Sign-up page is automatically translated to the default language of the browser if the translation is available in the locales. If the translation is not available in the locales, the page is provided in English. The English and Russian languages are available by default, other languages are to be added to the system configs. Contact your manager for configuration details. #### Transactions Now the *Remitter name* parameter is optional for transactions. It is possible to create and edit transactions without setting the parameter. *** ** * ** *** ### **Fixes** #### Banking Web Interface In some cases, the dynamic translation could not be performed correctly for the Web Interface. Now the issue is fixed. #### Identification requests An error occurred if an administrator deleted a document sent for verification. Now the *Identification requests* section is working correctly. --- language: "en" --- # \[2021\] Crassula Release Week 51 *core v.21.12.9-21.12.10* ![release_notes.png](https://help.crassula.io/__attachments/a_4b4ac69eb1c208c4ad6bc98d304551e38f0e275dbcd70e89c808be17801545fa/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## **Improvements** ### Payouts Payout initiation is improved for the Merchant Dashboard. Now the *Create*button is blocked when a payout is being processed. Thus, it is not possible for a merchant to create a duplicating payout. *** ** * ** *** ### **Fixes** #### Accounts In some cases, *Company* accounts could be opened as *Personal*when using the ClearBank integration. Now the issue is fixed. #### Cashback In some cases, the Cashback functionality could be applied to all currencies. Now the issue is fixed, and only the selected currency is considered. #### eCommerce payments The Checkout widget could be closed if an error message appeared. Now the issue is fixed. #### Transactions * Some BOL refund transactions were considered to be declined, though, they were successfully processed by the service prvider. The issue is fixed. * Some Unlimint transactions could not be processed correctly. Now *Pendign*transactions are succesfully authorized. --- language: "en" --- # \[2021\] Crassula Release Week 52 *core v.22.01.1-22.01.2* ![release_notes.png](https://help.crassula.io/__attachments/a_b8765e2a71ac64230f0bc101e8f668e8584cf24242c794f2f1ad0b0cdbeb3b8b/release_notes.png?cb=e2056af644ca607863e3f82756d119be) ## **New Features** ### Email notifications Now email notifications are sent to Clients when ClearBank and Aplonhub accounts are activated. The feature is enabled for accounts opened manually via the Banking Web Interface. #### Manual payments Now outgoing transfers can be created manually in the Administrative Panel. See [How to create a Transaction](https://crassula.atlassian.net/wiki/display/HELP/How+to+create+a+Transaction) for available options. *** ** * ** *** ### **Improvements** #### Account details The *Sort code* parameter is removed from the Administrative Panel. It is still possible to edit the setting in the system config. #### SWIFT payments Now *Address* , *City* , and *State*fields are validated when processing SWIFT payments. *** ** * ** *** ### **Fixes** #### Accounts * In some cases, a Card account could be considered primary restraining Clients from opening a new Standard account. Now Card accounts are separated from Standard accounts fixing the issue. * GBP accounts could be assigned to EU IBANs. Now the issue is fixed, and IBANs are set correctly. #### Payouts Now a payout transaction cannot be created in the Merchant Dashboard if a payout project is not configured. #### Web Interface The cache problem is fixed. Now correct user data is displayed when ordering a new card after logging into a new profile. --- language: "en" --- # Access roles ## Overview An access role defines the authorized activities of persons, companies, and company staff; the functionality allows to assign a client to a list of actions permitted in the Web Interface. By default, if there are no Standard access roles assigned to a client, all actions will be available. The **Access roles** tab provides the list of all access roles registered on the platform. ### Related pages [Accounts](https://help.crassula.io/knowledge/accounts.md) [Persons](https://help.crassula.io/knowledge/persons.md) [Limits](https://help.crassula.io/knowledge/limits.md) [Companies](https://help.crassula.io/knowledge/companies.md) [Company staff](https://help.crassula.io/knowledge/company-staff.md) [Transactions](https://help.crassula.io/knowledge/transactions.md) ## Opening the item Follow the steps below to see access role details : 1. Navigate to the Admin Panel. 2. Click **Banking**on the left sidebar. 3. Go to the **Access roles** menu item to open the **Access role list**. 4. Click **Edit**in an access role line to open its details. ## How to create an Access role Access roles have to be assigned to Persons, Companies, and Company staff. For example, a company employee can be assigned to a list of actions permitted in the Company's web interface. **To create an Access role** 1. Click **Add New** in the top-right corner of the **Access roles** tab. 2. Type in the name and description you want to set for the access role. 3. Select a user type the role will be applied to in the **Use Default For** drop-down menu. If the **None**option is selected, the role will not be applied automatically---manual assignment will be required. 4. Disable the **Enabled**checkbox if you want to activate the access role later. 5. Select the actions allowed for the access role in the **Roles**list (see the following sections for details on the actions) 6. Click **Create**to confirm the changes. Now the access role is created and ready to be assigned to a Client. ![859045895](https://help.crassula.io/__attachments/a_f368a16be8e9092e168e7f22048418b49a0a2e21c1c4f134f62111f4adb863ab/859045895?cb=a0f11e04a8b1368de9debea8c872d7a7) ## How to assign an Access role **To assign an Access role to a Client** 1. An existing Access role is required; see the previous section for details. 2. Navigate to the **Persons** /**Companies** /**Company staff**tab (depending on the type of Client you need the Access Role to be assigned to). 3. Click **Edit**to navigate to the corresponding Client's profile. 4. Navigate to the **Security** section of the profile for Persons and Companies. The step is omitted for **Company staff** profiles. 5. Click **Access roles**, and a list of created Access roles will be displayed in the drop-down menu. 6. Select an Access role you need to assign to the Client. 7. Click **Update**to apply the changes. ![Person's profile](https://help.crassula.io/__attachments/a_48b1c6435eb1845ec06d7b97bb744900b21aafb8496d071735ad8af35ec9113b/859045913?cb=5804a7a25115f60ae432f6cca5c2bf25) ## Component parameters ![access_roles.png](https://help.crassula.io/__attachments/a_0deb31934e7a569f0f51da0d2e0a9601b5930c0bb6f21e3e8832356409c1357f/access_roles.png?cb=a4f38744a6ea88ced18bf0e64abb2f1e) Access roles list | **Parameter** | **Description** | | |---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---| | **Id** | The column demonstrates unique role identification numbers in the Crassula system. | | | **Name** | The column includes access roles' names. | | | **Description** | An additional role description set while creation. | | | **Use Default For** | Defines the user type the role is applied to automatically: * None (not applied automatically) * Person (see [Persons](https://help.crassula.io/knowledge/persons.md) for details) * Company (see [Companies](https://help.crassula.io/knowledge/companies.md) for details) * Company staff (see [Company staff](https://help.crassula.io/knowledge/company-staff.md) for details) | | | **Enabled** | Defines whether the role status is *Enabled* or *Disabled.* | | | **Action** | Browse, edit, or delete role details. * Click **Edit**to open a role with the right to edit the details. * Click **Delete**to remove a role. | | | **Filters** | Search for access roles by name and status; multiple-choice is available. | | | **Add new** | Create an access role manually; see the following sections for details. | | | **Help** | Click to access the current page right from the Admin Panel. | | ## Configuring the component **Access role details** is the main panel of role information display and editing. ![access_role_edit.png](https://help.crassula.io/__attachments/a_0458fdf04ab22f6eb1674e04b4885f36dff92029d64fe1f08d7e0e4d32f061b5/access_role_edit.png?cb=f73e47b83fd9676ae6a793f2143cc6be) Edit an access role | **Parameter** | **Description** | |---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Name** | The name set during the role creation process. | | **Description** | Additional role description set during the creation process. | | **Use Default For** | Defines the user type the role is applied to automatically: * None (not applied automatically) * Person (see [Persons](https://crassula.atlassian.net/wiki/pages/resumedraft.action?draftId=847937593) for details) * Company (see [Companies](https://help.crassula.io/knowledge/companies.md) for details) * Company staff (see [Company staff](https://help.crassula.io/knowledge/company-staff.md) for details) | | **Enabled** | Defines whether the role status is *Enabled* or *Disabled*. | | **Roles** | Defines the actions allowed for the access role in the list: * **Client Account**provides access to the following actions: * List -- browse the account list. When disabled, the client will not be able to see or create accounts. * Requisites - browse account requisites and top up the account with a manual bank transfer. * View -- browse account details. * Create -- open a new account. * Close -- delete an account (see [Accounts](#) for details). * **Client Transfer** provides access to the following actions: * Cancel -- delete a drafted transfer * Dynamic -- dynamic transfers execution with variable parameters * List -- browse the executed transfers list. When disabled, the client will not be able to see the list of transfers and create new payments. * View -- browse the transfer details * Statement -- upload an account statement * Payslip -- send a transfer via the Payslip provider * SEPA-- send a transfer via the SEPA provider * Send -- send a drafted transfer * Internal -- send a transfer to another client * Swift -- send a transfer using SWIFT * Self -- transfer money between the Client's accounts * Card -- transfer money between the Client's cards * Local -- send local UK transfers in pounds * Crypto -- transfer cryptocurrency * **Client Balance**provides access to the following actions: * List -- browse the Client balance(s) * **Client Issued Card** provides access to the following actions: * Activate -- change the status of a new card to active * Block -- disable all transactions for a card * Change Pin -- set or update a card pin-code * Get -- browse issued cards details * Get Pin - browse issued cards' PIN codes * Create -- issue a new card * List -- browse all the issued cards. Make sure to disable the *Client Issued Card Settings\>Show* action to disable the Cards section in the Web Interface. * Top Up -- top up the card from an account / a card * Unblock -- enable all transactions for a blocked card * **Client Issued Card Settings**provides access to the following actions: * Show -- browse the card settings. Make sure to disable the *Client Issued Card\>List* action to disable the Cards section in the Web Interface. * Update -- edit the card settings * **Client Client Card**provides access to the cards used for account top-up: * List -- browse the cards that have been used for account top-up * View -- browse the card details that have been used for account top-up * Update -- edit a saved top-up card * Close -- disable a top-up card * Create -- save a card for further top-ups * Delete -- discard a saved top-up card * **Client Profile**provides access to the following actions: * View -- browse profile details with no right to edit * Update -- edit profile details * **Client Token** provides access to the following actions: * Create -- issue a personal key token * **Client Company** provides access to the following actions: * List -- browse the associated companies list * View -- browse the associated companies' details (see [Companies](#) for details) * Create -- create an associated company (see [Companies](#) for details) * **Client Company Staff** provides access to the following actions: * List -- browse the list of Company personnel (see [Company staff](#) for details) * **Client Exchange**provides access to the following actions: * Currency -- browse the currency of the executed exchange transactions * View -- browse the exchange transaction details * List -- browse the list of executed exchange transactions * Update -- change transaction details * **Client Document** provides access to the following actions: * List -- browse all the documents uploaded * Create -- create a new Client document * Update -- edit a document * Upload -- upload a new document * View -- browse the details of an uploaded document (see the Identification section of [First Steps in the Admin Panel](https://help.crassula.io/knowledge/first-steps-in-the-admin-panel.md) for additional information) * **Client Drafts**provides access to the following actions: * Confirm -- confirm a draft creation * Delete -- remove a transaction draft * Create -- add a transaction draft * **Client Existing Recipient**provides access to the following actions: * List -- browse the transfer history and the recipients * **Client Fee**provides access to the following actions: * Fees -- browse the fees applied to the Client * Transfer -- browse transfer fees * Currency -- browse exchange transaction fees * **Client Issued Card Holds**provides access to the following actions: * List -- browse all the card holds * **Client Issued Card Limit** provides access to the following actions: * List -- browse the limits applied * Create -- add a limit for card transactions * Delete - discard a limit * **Client Limit** provides access to the following actions: * List -- browse the limits applied to the Client (see [Limits](#) for details) * **Client Payout** (eCom) provides access to the following actions: * Create -- create a Payout payment to a client for POS transactions executed in a period * Parameters list -- browse the payout details and settings * **Person Email** provides access to the following actions: * List -- browse all the Client emails * Add -- add a new email to the Client's profile * Update -- change email details * Delete -- discard an email * Mark as primary -- set an email as a primary contact * Send verification code -- verify email and other transactions * **Person Phone** provides access to the following actions: * List -- browse all the Client emails * Add -- add a new email to the Client's profile * Update -- change email details * Delete -- discard an email * Mark as primary -- set an email as a primary contact * Send verification code -- verify email and other transactions * Verify -- verify a phone number using verification codes * **Client Push Notification Subscription** provides access to the following actions: * Create -- Add a subscription to transaction notifications * Delete -- discard a subscription * List -- browse active subscriptions * **Client Referral program** provides access to the [Referral program](https://help.crassula.io/knowledge/referral-codes.md): * List -- access referral codes * **Reports** provide access to the following actions: * Companies -- create and manage company transaction reports * Persons -- create and manage person transactions reports * Transactions -- create and manage transaction reports * **Client Fee FX markup** provides access to the following actions: * List -- browse all FX markups set for the Client * View -- browse markup details * Status update -- change the status of a markup * Create -- create a new markup * Update -- change markup details * Delete -- discard a markup * **Client Price list** provides access to the following actions: * List -- access the list of price lists * View -- browse price list details * Assign -- assign a price list * Delete -- discard a price list * **Client Fee Transfer Fees** provides access to the following actions: * List -- access the list of charged fees * View -- browse details of a charged fee * Create -- create a transfer fee * Update -- change a transfer fee * Delete -- discard a transfer fee * **Client Transfer Templates** provides access to the following actions: * List -- browse all transfer templates created by the Client * Create -- create a template * Update -- change a template * Delete -- discard a template * View -- browse templates details * **Client Vault** provides access to the following actions: * List -- access the list of Vaults * View -- browse Vault details * Create -- open a new Vault account * TopUp -- top up a Vault account * Withdrawal -- withdraw funds from a Vault account * Vaults -- access the list of Vaults in the Admin Panel | | **Help** | Click to access the current page right from the Admin Panel. | --- language: "en" --- # Access roles (Administration) ## Overview An administrative access role is a set of actions permitted for a group of Administrators. Creating several access roles with diverse configurations allows you to delegate responsibilities to Administrators within the Administrative Panel. For example, one group of Administrators is responsible for Banking support, while another one is in charge only of Card Products. The functionality is also applicable to grant administrative access to a sales agent or accountant, where the first one is only allowed to create new profiles and the latter is granted read-only access. The **Access roles** tab allows you to manage all administrative access roles registered at the platform. ### Related pages ## Opening the item Follow the steps below to open role details: 1. Navigate to the Admin Panel 2. Click **Administration**on the left sidebar 3. Go to the **Access roles** menu item to open the **Access role list**. 4. Click **Edit**in an access role line to open its details. ## How to create an Access role Access roles have to be assigned to Administrators for them to access the Administrative Panel functionality. **To create an administrative Access role** 1. Navigate to the Admin Panel. 2. Click **Administration**on the left sidebar. 3. Go to the **Access roles** menu item to open the **Access role list**. 4. Click **Add new** in the top right corner. 5. Set a **Name** for the role. 6. Add a descriptive phrase in the **Description** field to mark out the main functionality of the role. 7. Set the **Enabled** parameter to activate the role on creation. Disable the checkbox if you want to activate the access role later. 8. Select the actions allowed for the access role in the **Roles**list (see the following sections for details on the actions). 9. Click **Create**to confirm the changes. Now the Access role is created and ready to be assigned to an Administrator. ![create.png](https://help.crassula.io/__attachments/a_8857b5fc635eca682b23f5965896869c913743413277e4c93bad01ada096a486/create.png?cb=e8e90459e0254070910a57198ccca17e) Creating an Access role ## How to assign an Access role **To assign an Access role to an Administrator** 1. An existing Access role is required; see the previous section for details. 2. Navigate to the Admin Panel. 3. Click **Administration**on the left sidebar. 4. Go to the **Administrators** menu item to open the list of Administrators. 5. Click **Edit**to navigate to the corresponding Administrator. 6. Click the **Access roles**field. 7. The list of active Access roles will be demonstrated in the drop-down menu. 8. Select one or several Access roles you need to assign to the Administrator. 9. Click **Update**to apply the changes. ![assign.png](https://help.crassula.io/__attachments/a_35ce8d3330f3db03d07f52f2dcae4286206287bed6669bcee06db79b3e3dc5d7/assign.png?cb=0f365da799e629331b130de411b9a216) ## Component parameters ![list.png](https://help.crassula.io/__attachments/a_ffc5adc1069bce4cd7600ce3492bcac8e6f64ff8d76a2d065acf905af5b710b1/list.png?cb=8c9feace4e0345bbef006a1f9044e80c) Access role list | **Parameter** | **Description** | |-----------------|-------------------------------------------------------------------------------------------------------------------------------------| | **Id** | The column demonstrates unique role identification numbers in the Crassula system. | | **Name** | The column includes Access role names. | | **Description** | Additional role description defined on creation. | | **Enabled** | Defines whether the role status is *Enabled* or *Disabled.* | | **Action** | Edit or delete role details. * Click **Edit**to open a role with the right to edit the details. * Click **Delete**to remove a role. | | **Filters** | Search for Access roles by name and status; multiple-choice is available. | | **Add new** | Create an Access role manually; see the previous sections for details. | | **Help** | Click to access the current page right from the Admin Panel. | ## Configuring the component **Access role details** is the main panel of role information display and editing. ![create.png](https://help.crassula.io/__attachments/a_8857b5fc635eca682b23f5965896869c913743413277e4c93bad01ada096a486/create.png?cb=e8e90459e0254070910a57198ccca17e) Access role details | **Parameter** | **Description** | |-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Name** | The name set during the role creation process. | | **Description** | Additional role description set during the creation process. | | **Enabled** | Defines whether the role status is *Enabled* or *Disabled*. | | **Roles** | Defines the administrative actions allowed for the role. The most common actions are defined as follows: * All---unrestricted access to the component. * List---browse the list of active component items. * Create---create an item. * Edit---edit an item. * Show---browse item details. * Export---download the list of items. * Delete---remove an item. The actions are grouped according to the existing Administrative Panel tabs and windows. All special actions are defined under the corresponding group. * **API** parameters provide access to the *API* menu of the Administrative Panel. * API keys---manage items within the *API keys* window. * Access roles---manage items within the *Access roles* window * **Administration** parameters provide access to the *Administration* menu of the Administrative Panel. * Activity log---manage items within the *Activity log* window. * Administrators---manage items within the *Administrators* window. * Access roles---manage items within the *Access roles* window. * Access groups---manage items within the *Access groups* window. * Authentication log---manage items within the *Authentication log* window. * Authentications---manage items within the *Authentications* window. * Legal documents---manage items within the *Legal documents*window. * Legal document announcements---manage items within the *Legal documents announcements*window. * Dictionary---manage items within the *Dictionary*window. * Holidays---manage items within the *Holidays*window. * Transfer provider operation time---manage items within the *Transfer provider operation time*window. * Legal document versions---manage the history of document versions in the *Legal documents* section. * Notifications * Subscribe---receive email reports on activity in the Administrative Panel. * **Banking** parameters provide access to the *Banking*menu of the Administrative Panel: * Persons---manage items within the *Persons*window. * Scan---perform compliance screening in the *Person details* window. If not set, the action will not be available for the role. The functionality is available if the *PEP\&Sanctions scanning* feature is enabled. Contact your manager for configuration details. * Companies---manage items within the *Companies*window. * Scan---perform compliance screening in the *Person details* window. If not set, the action will not be available for the role. The functionality is available if the *PEP\&Sanctions scanning* feature is enabled. Contact your manager for configuration details. * Access roles---manage items within the *Access roles*window. * Company staff---manage items within the *Company staff*window. * Country Groups---manage items within the *Country Groups*window. * Accounts---manage items within the *Accounts*window. * Activate---activate and reactivate accounts. If not set, the action will not be available for the role. * Mark As Primary---manage account priority status. * Close---terminate accounts (such accounts remain seen in the Crassula system) * Iban---generate IBANs for accounts. * Update Balance---manually perform internal deposit transactions. * Statement---download the detailed list of account transactions. * Metadata---access the *Metadata* tab of the *Account details* window. * Decline---decline opening of an additional account. Additional accounts can be created in the *Waiting for approval* status if the functionality is enabled in the system configs---the action allows rejection of such accounts. If not set, the action will not be available for the role. * Accounts (waiting for approval)---manage items within the *Accounts (waiting for approval)*window. * Activate---activate and reactivate accounts. If not set, the action will not be available for the role. * Mark As Primary---manage account priority status. * Close---terminate accounts (such accounts remain seen in the Crassula system) * Iban---generate IBANs for accounts. * Update Balance---manually perform internal deposit transactions. * Statement---download the detailed list of account transactions. * Metadata---access the *Metadata* tab of the *Account details* window. * Decline---decline opening of an additional account. Additional accounts can be created in the *Waiting for approval* status if the functionality is enabled in the system configs---the action allows you to reject such accounts. If not set, the action will not be available for the role. * Vaults---manage items within the *Vaults*window. * Activate---activate and reactivate accounts. If not set, the action will not be visible for the role. * Mark As Primary---manage account priority status. * Close---terminate accounts (such accounts remain seen in the Crassula system) * Iban---generate IBANs for accounts. * Update Balance---manually perform internal deposit transactions. * Statement---download the detailed list of account transactions. * Metadata---access the *Metadata* tab of the *Account details* window. * Decline---decline opening of an additional account. Additional accounts can be created in the *Waiting for approval* status if the functionality is enabled in the system configs---the action allows you to reject such accounts. If not set, the action will not be available for the role. * Saved top-up cards---manage items within the *Saved top-up cards*window. * Transactions---manage items within the *Transactions*window. * Process---approve recall transactions. * State---manually change transaction state. * Resolve---approve or reject lock-up transactions. The functionality of lock-up transactions is available only for the Railsr service provider. If not set, the action will not be available for the role. * Refund---return funds to the account. If not set, the action will not be visible for the role. * Recall---revoke a refunded transaction. * Cancel---decline the transaction execution. If not set, the action will not be visible for the role. * Set Beneficiary---change beneficiary details in the *Edit* mode. * Sync Status---synchronize transaction statuses between the Admin Panel and service provider. If not set, the action will not be visible for the role. * Transactions (pre-approval)---manage items within the *Transactions (pre-approval)*window. * Process---approve recall transactions. * State---manually change transaction state. * Resolve---approve or reject lock-up transactions. The functionality of lock-up transactions is available only for the Railsr service provider. If not set, the action will not be available for the role. * Refund---return funds to the account. If not set, the action will not be visible for the role. * Recall---revoke a refunded transaction. * Cancel---decline the transaction execution. If not set, the action will not be visible for the role. * Set Beneficiary---change beneficiary details in the *Edit* mode. * Transactions (action required)---manage items within the *Transactions (action required)*window. * Process---approve recall transactions. * State---manually change transaction state. * Resolve---approve or reject lock-up transactions. The functionality of lock-up transactions is available only for the Railsr service provider. If not set, the action will not be available for the role. * Refund---return funds to the account. If not set, the action will not be visible for the role. * Recall---revoke a refunded transaction. * Cancel---decline the transaction execution. If not set, the action will not be visible for the role. * Set Beneficiary---change beneficiary details in the *Edit* mode. * Transactions (undetermined)---manage items within the *Transactions (undetermined)*window. * Process---approve recall transactions. * State---manually change transaction state. * Resolve---approve or reject lock-up transactions. The functionality of lock-up transactions is available only for the Railsr service provider. If not set, the action will not be available for the role. * Refund---return funds to the account. If not set, the action will not be visible for the role. * Recall---revoke a refunded transaction. * Cancel---decline the transaction execution. If not set, the action will not be visible for the role. * Set Beneficiary---change beneficiary details in the *Edit* mode. * Identification requests---manage items within the *Identification requests*window. * Zip---download the request details as an archive. If not set, the *Download* action will not be visible for the role. * Approve---change the identification request status to *Approved*. If not set, the action will not be visible for the role. * Reject---change the identification request status to *Rejected*. If not set, the action will not be visible for the role. * Reject Finally---permanently change the identification request status to *Rejected*. If not set, the action will not be visible for the role. * Expiring documents---manage items within the *Expiring documents*window. * Price lists---manage items within the *Price lists*window. * Publish---activate price lists. If not set, the action will not be visible for the role. * Disable---deactivate price lists. If not set, the action will not be visible for the role. * Clone---create a copy of a price list. If not set, the action will not be visible for the role. * PEP \& sanctions---manage items within the *PEP \& sanctions*window. * Limits---manage items within the *Limits*window. * Check---scan past transactions for limit breaches. If not set, the action will not be visible for the role. * Triggered limits---manage items within the *Triggered limits*window. * Application forms---manage items within the *Application forms*window. * Client application forms---manage items within the *Client application forms*window. * Answers---access the answers provided by clients. * Approve---verify and finalize the answers. * Decline---reject the answers. * Request---repeat the request. * Batch payments---manage items within the *Batch payments*window. * Start---launch the batch payment. If not set, the action will not be visible for the role. * Continue---resume batch payment processing in case of iteration parts being declined. * Cancel---delete the batch payment. * File Example---download CSV and XLS file examples. * Issues---manage items within the *Issues*window. * Approve---approve the resolution of an issue. * Reject---approve the resolution of an issue. * Request Update---request the resolution status. * Assign To Me---set the current Admin profile as the issue assignee. * Clients---access the list of active clients in all the client-related fields. If not set, client names will not be suggested in a drop-down list when filling *Client* or *Name/Surname* fields. * Show Client---access the extended list of details. * List in reports filter---access active clients as a drop-down list when configuring report filters in the *Reports* section of the Admin Panel. The *List* action must be set to true. * Client notes---manage items within the *Notes* tab of the *Person* and *Company*profiles. * Provider numbers---manage provider details within the *Persons* and *Companies*windows. * Disable---disable account IBANs in the *Provider account numbers* field of the *Account* details window. The functionality can be used for Financial accounts with multiple IBANs. If not set, the action will not be visible for the role. * Transactions (outgoing)---manage outgoing transactions available in *Person* and *Company*profiles. * Client Documents---manage items within the *Documents* tab of the *Person* and *Company*profiles. * Approve---approve documents attached to client profiles within the *Documents* tab of the *Person* and *Company* profile details. * Reject---decline documents attached to client profiles within the *Documents* tab of the *Person* and *Company* profile details. * Download---import documents attached to client profiles within the *Documents* tab of the *Person* and *Company* profile details. * Fees---manage items within the *Transfer fees* tab of the *Price lists*window. * Issued Card Fees---manage items within the *Issued card fees* tab of the *Price lists*window. * Recurring fees---manage items within the *Recurring fees* tab of the *Price lists*window. * FX Markup Fees---manage items within the *FX markup fees* tab of the *Price lists*window. * Cashback---manage items within the *Cashback* tab of the *Price lists*window. * VaultRates---manage items within the *Vault rates* tab of the *Price lists*window. * Change Verification Level Fees---manage items within the *Change verification level fees* tab of the *Price lists*window. * Change Person Subscription Plan Fees---manage Price list rules for subscriptions of the Person type. * Change Company Subscription Plan Fees---manage Price list rules for subscriptions of the Company type. * Two-factor auth methods---manage items within the *Two-factor auth methods* tab of *Person*profiles. * Company clients---manage items within the *Clients* tab of the *Company*profiles. * Client legal agreements---manage items within the *Legal agreements* tab of the *Person* and *Company*profiles. * Client account provider configuration---manage account providers within the *Persons* and *Companies*windows. * Application form questions---manage questions within the *Application forms*window. * Application form question option---manage question options within the *Application forms*window. * Application form answers---manage answers within the *Client application forms*window. * Batch payment iteration---manage items within the *Batch payment requests* tab of the *Batch payments*window. * Batch payment recipient---manage items within the *Recipients* tab of the *Batch payments*window. * Tags---manage tags available in *Person* and *Company*profiles. * **Card Issuing** parameters provide access to the *Card issuing*menu of the Administrative Panel: * Issued cards---manage items within the *Issued cards*window. * Activate---manually activate client cards. If not set, the action will not be visible for the role. * Suspend---suspend client cards. If not set, the action will not be visible for the role. * Block---freeze client cards. If not set, the action will not be visible for the role. * Request---send a request for issuing a *New* or *Preordered* card. The functionality is applicable when a manual request to a service provider is required. If not set, the action will not be visible for the role * Decline---cancel a request for issuing a *New* or *Preordered* card. If not set, the action will not be visible for the role * Check Identification Status---run document verification required by some service providers. If not set, the action will not be visible for the role * Submit Documents---manually attach documents required for card issuing. If not set, the action will not be visible for the role * Update Settings---manage items within the *Settings* tab of the *Issued Card details* window. * Recheck Status---request card status update from service providers in the *Issued Card details* window. If not set, the action will not be visible for the role. * Import Transactions---download the list of card transactions. * Issued card holds---manage items within the *Issued card holds*window. * Issued card transactions---manage items within the *Issued card transactions*window. * Approve---approve transaction match and close the review. * Clearing process log---manage items within the *Clearing process log*window. * Issued card failed auth---manage items within the *Issued card failed auth*window. * Card transfer requests---manage items within the *Card transfer requests*window. * Clearing import notices---manage items within the *Clearing import notices*window. * **Exchange** parameters provide access to the *Exchange*menu of the Administrative Panel: * Rate history---manage items within the *Rate history*window. * Requests---manage items within the *Requests*window. * Process---review requests. If not set, the action will not be visible for the role. * Approve---approve requests. If not set, the action will not be visible for the role. * Cancel---decline requests. If not set, the action will not be visible for the role. * Complete---fill requests. If not set, the action will not be visible for the role. * Assign---assign a request to other Administrators. If not set, the action will not be visible for the role. * Orders---manage items within the *Orders*window. * Transactions---manage items within the *Transactions*window. * Markup fees---manage items within the *Markup fees*window. * **Reports** parameter is applied to the whole *Reports*menu of the Administrative Panel: * Report filter client---ability to filter reports by client. * **Reports Banking** parameters are applied to *Banking*reports: * Accounting---manage items within the *Accounting*window. * Currency turnover---manage items within the *Currency turnover*window. * Fees---manage items within the *Fees*window. | | **Help** | Click to access the current page right from the Admin Panel. | --- language: "en" --- # Accounting (Banking reports) ## Overview An **Accounting**report provides information about client accounts, including balances, incomes, and fees charged from the accounts. The report typically includes details such as the account number, account name, opening balance, closing balance, transfers made, and fees charged. The **Accounting**report is generated for a specific period, such as daily, weekly, monthly, or yearly, and may be customized to include specific accounts or client groups. Among the specialized reports available, the **End of day statement** format is tailored to provide a snapshot of daily financial activities. For users requiring automated integration, this statement can now be retrieved via API in XML or JSON formats, adhering to the ISO20022 standard. For full details on utilizing this type of report, including API parameters, response formats, and example requests, please refer to `POST /api/clients/{clientId}/statement-requests/{_format}` and `GET /api/clients/{clientId}/statement-requests/{id}` API method descriptions in the [Bank API docs](https://docs.crassula.io/client). The report is a crucial tool for White Labels to manage their clients' accounts' financial performance. The report provides valuable insights into the White Label's account performance and helps White Labels develop strategies to enhance their profitability while ensuring compliance with regulatory requirements. ### Related pages [Accounts](https://help.crassula.io/knowledge/accounts.md) [Price lists](https://help.crassula.io/knowledge/price-lists.md) [Transactions](https://help.crassula.io/knowledge/transactions.md) ## Opening the item Follow the steps below to access Accounting reports: 1. Navigate to the **Reports** section of the Admin Panel. 2. Click **Banking**on the left sidebar 3. Go to the **Accounting**menu item. ## How to export a report Most of the banking reports are sufficient without being exported, though there is always a possibility to export them as an `.xls`, `.csv`, `.json`, or `.xml` file. **To export a report** 1. Navigate to the **Accounting** reports window. 2. Set the **Period start** and **Period end** parameters to define the time period that must be considered. The parameters are mandatory. 3. Type in a client name in the **Client**field if you need the report to contain details of an exact client. 4. Set the **Account status** parameter to define which client *Aggregated* status must be considered in the report. **Active** and **Suspended**statuses are included by default. 5. Set the **Client type** parameter to define whether **Persons** and/or **Companies**must be considered in the report. Both client types are included by default. 6. Set the **Currency** parameter to filter out accounts by currency. The parameter is set to **EUR** by default. 7. Click **Filter**. The list will be updated according to the configuration. 8. Click **Download**and select a file type for export if you need to access the report outside of the Admin Panel. ## Component parameters ![accounting.png](https://help.crassula.io/__attachments/a_00b092251f2ce3346ee3a5443534b87eea5ac7d2508c56ab5cc9168c83f92788/accounting.png?cb=1777737b31dae46e3ead026a36838f05) Accounting report | **Parameter** | **Description** | |----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Beneficiary** | The name of the account owner. | | **Beneficiary status** | Account owner *aggregated status* that defines whether there are restrictions set by KYC Administrators or Identification providers. | | **Account Number** | Account number, IBAN, or crypto wallet address. | | **Currency** | Payment currency. | | **Opening Balance** | Account balance at the period start. | | **Total interledger received** | The total amount of payments received from interledger accounts. The interledger functionality is applicable when making payments between different payment networks and systems (if enabled). | | **Total interledger sent** | The total amount of payments sent to interledger accounts. The interledger functionality is applicable when making payments between different payment networks and systems (if enabled). | | **Total transfers received** | The total amount of payments received during the defined period. | | **Total transfers sent** | The total amount of payments made during the defined period. | | **Total commission accrued** | The amount of fees received by the White Label's account. | | **Total commission charged** | The total amount of fees charged from the client during the defined period. | | **Total sent via external providers** | The total amount of external payments made in the account. | | **Transfers received via internal** | The total amount of internal payments received in the account, i.e., payments received from other White Label clients. | | **Transfers sent via internal** | The total amount of internal payments made in the account, i.e., payments sent to other White Label clients. | | **Commission accrued via internal** | The amount of fees received by the White Label's account for internal payments, i.e., payments between White Label clients. | | **Commission charged via internal** | The total amount of fees charged from the client for internal payments, i.e., payments between White Label clients. | | **Transfers received via sepa_manual** | The total amount of manual payments received during the defined period. The parameter is available only if there are payments made by the **sepa_manual** service provider. See [Manual payments](https://help.crassula.io/knowledge/manual-swift-and-sepa-payments.md) for details. | | **Transfers sent via sepa_manual** | The total amount of manual payments sent during the defined period. The parameter is available only if there are payments made by the **sepa_manual** service provider. See [Manual payments](https://help.crassula.io/knowledge/manual-swift-and-sepa-payments.md) for details. | | **Commission accrued via sepa_manual** | The amount of fees received by the White Label's account for manual SEPA payments. See [Manual payments](https://help.crassula.io/knowledge/manual-swift-and-sepa-payments.md) for details. | | **Commission charged via sepa_manual** | The total amount of fees charged from the client for manual SEPA payments. See [Manual payments](https://help.crassula.io/knowledge/manual-swift-and-sepa-payments.md) for details. | | **Deposited via cards** | The total amount of funds deposited with a card, i.e., the deposits made in the Web Interface. | | **Deposited by operators** | The total amount of funds deposited by an administrator, i.e., the deposits made in the Admin Panel. | | **Withdrawn by operators** | The total amount of funds withdrawn by an administrator, i.e., the withdrawals made in the Admin Panel. | | **Refunds** | The total amount of refunds during the period. | | **Recalls** | The total amount of recalls during the period. | | **Converted from currency** | The total amount of conversion transactions from the account currency. | | **Converted to currency** | The total amount of conversion transactions to the account currency. | | **Card purchases** | The total amount of card purchases during the period. | | **Card withdrawals** | The total amount of card withdrawals during the period | | **Closing balance** | Account balance at the period end. | | **Outgoing pending operations** | Transactions that have been initiated but not yet fully processed or cleared from the account. These may include payments, transfers, or other debits that reduce the available balance but have not been finalized. | | **Incoming pending operations** | Transactions that have been initiated but not yet fully processed or cleared into the account. These include deposits, transfers, or other credits that increase the available balance but are still pending finalization. | | **Actual balance** | Represents the current available balance calculated according to the following formula: `actual balance = (closing balance) - (outgoing pending operations)` | --- language: "en" --- # Accounts ## Overview An account allows the end-users to deposit and withdraw funds for daily transactions. In the Crassula system, all accounts are opened by service providers and do not require any assistance from Administrators; though, it is possible to open an account manually for exceptional cases. The **Accounts** tab provides the list of all accounts registered on the platform. Find, review, and edit account details using the **Accounts**tab. ### Related pages [Persons](https://help.crassula.io/knowledge/persons.md) [Price Lists](https://help.crassula.io/knowledge/price-lists.md) [Transactions](https://help.crassula.io/knowledge/transactions.md) [Identification requests](https://help.crassula.io/knowledge/identification-requests.md) [First Steps in the Admin Panel](https://help.crassula.io/knowledge/first-steps-in-the-admin-panel.md) ## Opening the item Follow the steps below to access the account details: 1. Navigate to the Admin Panel. 2. Click **Banking**on the left sidebar. 3. Go to the **Accounts** menu item to open the **Accounts List**. 4. Click **Show** or an account number in the **Number**column to open the details. ## How to open an Account **To open an account** 1. Navigate to the **Accounts**menu item. 2. Click **Add New** in the top-right corner of the tab. 3. Type in a Client's name or email to find the Client you want to open an account for. The field is mandatory, and an existing client is required. If the Client is not registered yet, see [Persons](https://help.crassula.io/knowledge/persons.md) and [Companies](https://help.crassula.io/knowledge/companies.md) for details. 4. Type in the account name in the **Name**field. 5. Select the type of account from the **Type**drop-down menu. 6. The **Fee activated at** parameter is optional. Set the parameter if a Price list is available; see [Price lists](https://help.crassula.io/knowledge/price-lists.md) for details. 7. Click **Create**to confirm the account opening. An internal account number will be generated. ![Account_opening.png](https://help.crassula.io/__attachments/a_9f540aea73251c69553d9971aa4982b46cbcfe3c4e2793cc387abfa508656921/Account_opening.png?cb=972f282aa4df9d6731586330fa17df64) ## Component parameters ![accounts.png](https://help.crassula.io/__attachments/a_e12da5514db7a0ffef3675242ad8622cb7eb2c3d98eb924d1fa6b1f12bc9c9ab/accounts.png?cb=0db01f060d09f9b261a8574f09e68267) Accounts list | **Parameter** | **Description** | |----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Number** | The column demonstrates internal account numbers. At the same time, internal account numbers are used as entity IDs that are available in the Activity log section. Click a *Number* to open the Account details. | | **Client** | The column includes the names of clients and the accounts are assigned. Click a *Client Name* to open profile details. | | **Holder** | An additional account holder who is entitled to use the account via the Web and Mobile Interfaces. The parameter was initially designed for financial accounts (Account type = Finance). Similar to the company staff functionality, it allows a financial institution to grant another company access to its financial account to generate IBANs and perform transactions via API. The account remains under the financial institution's ownership and license but becomes accessible to the other company for specific operations. The service is provided via the Administrative Panel and does not grant access to the whole profile. | | **Name** | Account names are demonstrated in the column. The names of additional accounts are set by the Client at the moment of account opening. | | **Type** | Three main account types are available for opening: * **Standard**accounts are checking fiat accounts for everyday tasks. * **Finance** accounts work as custody fiat accounts. Therefore, such accounts can include several IBANs generated via API, but none of them would be personalized or have their own balance. A Finance account can be used as a custody placeholder for further development on the White Label's side. Finance accounts can be used as Primary accounts. Not every integrated provider supports the functionality. Contact your manager for additional details. * **Crypto**accounts record individual coin ownership. | | **Primary** | Account priority status. Mostly, Primary accounts are opened first and used for fee charging. Click **Mark as primary** to set the account priority to Primary. Only one Primary account is allowed per client. | | **Status** | Account verification status: * *New* (recently opened, waiting for [Identification](https://help.crassula.io/knowledge/identification-requests.md)) * *Active* (fully functioning account, Identification is complete) * *Suspended*(outgoing transfers are temporarily blocked until document submission; once the required documents are provided, it is possible to activate the account again) * *Awaiting provider number* (the provider is processing the IBAN generation; the status usage depends on the external provider settings) * *Waiting for approval* (temporarily inactive, document verification is processing) * *Rejected*(permanently blocked, no outgoing transfers allowed) * *Closed*(the account is successfully closed) An account is to have a zero balance in order to be closed. Navigate to the **Accounts list** and click **Close**to settle an account. Make sure to differentiate **Status** from **Aggregated status** available in [Banking Reports](https://help.crassula.io/knowledge/banking-reports.md). Aggregated status is set according to the following logic: if state = blocked then blocked if state = suspended then suspended if is_person and verification_status = identified then active if is_company and verification_status = identified then active else pending | | **Provider** | The name of the account opening provider. * A Provider is an external service delivering additional functionality via APIs. As an example, the account opening service can be held by Railsr, Litas Sepa, Intercash, and others. Therefore, Crassula delivers various banking solutions that do not require manual assistance. Accounts with no service provider defined in the **Provider** field are created without account details and can be used for manual transactions. When a manual payment is sent from such accounts, it is processed virtually with no real funds engaged: it is up to the White Label to choose a method of how to deposit real funds to the recipient's account. Additionally, a White Label can manually generate IBANs for such accounts, though other account details will not be visible in the UI. | | **Provider currency** | Account currency (displayed when provided) set at the moment of account opening. The parameter is available only for mono-currency accounts. | | **Provider currencies (plural)** | Account currencies (displayed when provided). The parameter is available only for multi-currency accounts. If there are no currencies selected at the moment of account opening, they are set according to the system configs. | | **Provider number** | An IBAN generated by the financial service provider. Once the IBAN is generated, it is not possible to change it. | | **Action** | Show or edit account details. * Click **Show**to open the account details without the ability to edit them. * Click **Edit** to open a profile with the right to edit the details. * Click **Activate**for account activation. Client identification is recommended to be complete. * Click **Reactivate**to activate a closed account. * Click **Close**to deactivate the account. Profile and accounts are provided with their own unrelated states. Therefore, both profile and account statuses are to be changed in order to set restrictions for a Client. Account information remains in the Crassula system even if the account is closed by the Client or Administrator. * Click **Deposit**to create a transaction deposit. The Deposit action allows administrators to execute account deposits in case of Provider execution delays. The **Deposit**action has no "real-money" basis; therefore, it should be used in exceptional cases, and the Provider deposit transaction is to be finally executed. * Click **Generate IBAN** to assign an IBAN to the account. Applied when the service provider has not generated an IBAN. * Click **Suspend** / **Unsuspend**to change the account status correspondingly. The button is available for all Clearbank accounts except for GBP Virtual. | | **Filters** | Search for accounts by certain parameters. Search is filtered by the following parameters; multiple-choice is available: * *Number* - a unique account number in the system; * *Provider Number* - the account number (IBAN) in the Provider system; * *Type* -- standard / finance / crypto; * *Status* - account status according to verification details; * *Provider Name* - the account Provider name; * *Provider Currency* - account currency; * *Client*-- the name in the Client profile; * *Holder*-- the name of an additional account holder; * *Dormant*- filter out accounts that have had no financial activity for a defined period of time. The time period after which the account is considered dormant can be set in the system configs. * *Balance Reconciliation* - filter out accounts that have/do not have inequality in Provider and Crasula balances. * *Client Tags* - filter out accounts by tags set in profiles of the associated clients. | | **Add new** | Open an account manually, see the following sections for details | | **Help** | Click to access the current page right from the Admin Panel. | ## Configuring the component **Account details** is the main panel of account information display and editing. ![account_details.png](https://help.crassula.io/__attachments/a_fc204490fb674b8278c0cecbae6b6b08d6bbe07ee75f3a14ec0fcdbb27bf657b/account_details.png?cb=61614e3889d5804e104d4bfecb9d3572) Account details | **Parameter** | **Description** | |------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Details** | Account information, including the Client name, account number, and account type. The field includes the following special parameters: * Status changed by---defines the last person who changed the account status. For example, an administrator who activated, suspended, or unsuspended the account. * Last charge date---date and time when the last recurring fee was charged. * Fee activated at---date and time when the recurring fee was activated. All further fee transactions will be initiated on the activation date. The parameter value depends on the *Automatic fee activation* parameter. * Automatic fee activation---the parameter defines which day of the month will be considered as the fee activation date and initiate fee calculation. All further fee transactions will be initiated on the activation date. The following options can be enabled in the system configs: * Account activation time---The fee activation time will be set to the date of account activation. Recurring fee calculation will be performed starting from the date. * First day of the month---The *Fee activation date* will be set to the first day of the month when the account was created. For example, if the account was opened on 10.05.2022, the fee activation date will be set to 01.05.2022, and the fee calculation will start from the first day of the month. * Disabled---the account fee will not be activated automatically. | | **Statement** | Download a list of account transactions for a selected period. **To export a statement** 1. Set the **Currencies**field. Transactions in excluded currencies will not be visible in the report. The functionality is available only for multicurrency accounts. 2. Set the starting and ending dates for the transactions. 3. Select the **Format field** to define the required format (PDF or XLS); 4. Click **Download**to export the account statement. The system will process large reports and will inform the user with the **Export in progress** message. Once the processing is done, the download will start automatically. It is recommended to keep the window open. | | **Provider** | Account provider details, such as the following: * Provider name---the name of a service provider attending the account. * Provider currency---the account currency set in the provider system. The field includes the asset name, short name, and network of a cryptocurrency if applicable. * Provider external ID---an ID set for the account in the provider system. * Provider number---an IBAN provided for the account. * Provider currencies---a list of currencies supported by the account. | | **Provider account numbers** | Account numbers delivered by the service provider. The field displays all account numbers, currencies, and requisites for the opened account; a multi-currency account can be provided with several account numbers. There is an additional parameter available for the Clear Bank service provider: * **BIC code** is available for Clear Bank Multicurrency accounts. If the user selects the Clear Bank Real or Clear Bank Virtual provider, the field should be blank. BIC codes can be different for different accounts. | | **Balances** | Account balance in detail: * Currency---account currency. * Current---total account balance including holds. * Reserved---hold transactions. * Available---account balance available for transactions. * Provider---account balance according to the service provider. The functionality is available only for ClearJunctionReal, ClearBankRealGbp, and ClearBankRealMccy providers. Compare the values in the Provider and Available columns and click **Synchronization** in case of inequality. | | **Account Transaction Synchronizations** | The section provides a detailed report of transaction synchronization performed between Crassula and Railsr. Wait for the report to be processed (`Success` and `Failed` states) and click **Show more** for transaction comparison details. See [Transaction synchronizations](https://help.crassula.io/knowledge/transaction-synchronizations.md) for additional details. | | **Transactions** | Recent account transactions list (see Statement for the detailed list). * **Synchronization** ---click to synchronize the transactions with an external provider account. Once the transactions list is compared to the list of provider transactions, you can see a detailed report in the **Account Transaction Synchronizations** section. The functionality is available only for Railsr accounts. See [Transaction synchronizations](https://help.crassula.io/knowledge/transaction-synchronizations.md) for additional details. | | **Cards** | The field demonstrates all cards issued to the account | | **Top sidebar** | * **Metadata**is an API connection to external service Providers. If any external service has been used, the API link is demonstrated in the tab. * **Provider config** connects an account to the service provider using unique credentials. The functionality is available only for accounts that require manual configuration. See [Provider config](https://crassula.atlassian.net/wiki/spaces/HELP/pages/edit-v2/847970364#Provider-config) for additional details. * **Help**: access the current page right from the Admin Panel. * **Logs**: access logging details of every update sent to the service provider. Currently, the functionality is supported by all CurrencyCloud accounts and ClearJunction accounts opened for persons. | ### Provider config The tab includes functionality for managing accounts that should be manually connected to service providers, such as IFX Real, by linking the account with the provider's system and IBANs. While this currently applies to IFX Real, additional providers will be added in the future. ![provider_config.png](https://help.crassula.io/__attachments/a_049731797b78b8d794eb998d0a1402f1c6b92872295bfeaab98beee079923ff5/provider_config.png?cb=c9bc55a3bb3325f8da04030383ab1933) #### Manual Credentials Setup * Administrators are required to log into the provider's dashboard, retrieve the necessary credentials, and enter them into the "Provider Config" section of Crassula's Admin Panel. Once this step is completed, the account will be connected to the service provider and fully functional. Make sure administrators are provided with the **Accounts** \>**Provider config** access role. Editing is restricted and available only for Super Admins. ## Useful tips * Use filters in the Account List top-right corner for better navigation. * Click **Actions** \> **Edit**in the Account Details top-right corner to change the account details. --- language: "en" --- # Accounts (Mobile Interface) The Primary account is opened automatically once the user profile is created. All additional accounts are not limited in quantity and can be opened manually via the Mobile Interface. Select an account from the list to set it as default. **To open an account** 1. Click **Account** in the top-left corner of the **Home** page. The window with the list of existing accounts will be opened. 2. Click **+ New**in the top-right corner. 3. Set the account name in the text field. 4. Click **Create account** to confirm account opening. 5. Once the new account is opened, its details appear in the **Accounts** list. ![accounts.jpg](https://help.crassula.io/__attachments/a_522673fd19576c86b42a0ee0234bf9a96e9acb0112c3bc38dac313ce232edb17/accounts.jpg?cb=df433b1104bd2765b9dd7b87ca5021d4) --- language: "en" --- # Accounts (Web Interface) The Primary account is opened automatically once the user profile is created. All additional accounts are not limited in quantity and can be opened manually via the **Web Interface**. **To open an account** 1. Click the **Accounts** tab in the top sidebar. The window with the list of existing accounts will be opened. 2. Click **New Account**in the top sidebar above the list of accounts. The action is also available in the Dashboard's quick-access field. 3. Set the account name in the free-text field. 4. Click **Create Account** to confirm account opening. 5. Once the new account is opened, its details will appear in the **All Accounts** list. ![new_account.png](https://help.crassula.io/__attachments/a_40c7fd702864228a6dde0ee3fd717b00a7a6fd36d7afdcee3a97ed3715a81b3d/new_account.png?cb=9c75de558dc8813250c201869559e4a3) Click **Account details** in the list of active accounts to access the account details, such as **Beneficiary Name** , **Bank** , and **IBAN**. Account information remains in the \ system even if the account is closed by the Client or Administrator. --- language: "en" --- # Activity log ## Overview The **Activity Log** records all actions performed by administrators within the Admin Panel, providing a comprehensive audit trail of system changes. This log helps monitor administrative activities, track modifications, and ensure compliance with internal security policies. This section captures and displays a chronological record of changes made by administrators. Each entry includes essential metadata such as timestamps, affected entities, and descriptions of modifications. ![activity_log.png](https://help.crassula.io/__attachments/a_ac9239cb899e3fa27b09d96d5281ca1b1550204ccfffb6f01d13c9fb9680ebbf/activity_log.png?cb=138404ad7e0c149e97f5be6202ad7929) ## How to Access the Activity Log 1. Navigate tothe **Admin Panel**. 2. Go to the**Administration** section. 3. Select the**Activity Log** menu item. ## Parameters | **Parameter** | **Description** | |-------------------|---------------------------------------------------------------------------------------| | **Created At** | The timestamp when the action was recorded. | | **Administrator** | The administrator who performed the action. | | **IP Address** | The IP address from which the action was made. | | **Description** | A summary of the change or action performed. | | **Changes** | A detailed breakdown of the specific modifications made to an entity. | | **Filters** | Allows narrowing down logs based on Created At, Administrator, Section, or Entity ID. | --- language: "en" --- # Activity log \* ## Overview The **Activity Log** records all actions performed by administrators within the Admin Panel, providing a comprehensive audit trail of system changes. This log helps monitor administrative activities, track modifications, and ensure compliance with internal security policies. This section captures and displays a chronological record of changes made by administrators. Each entry includes essential metadata such as timestamps, affected entities, and descriptions of modifications. ![activity_log.png](https://help.crassula.io/__attachments/a_ac9239cb899e3fa27b09d96d5281ca1b1550204ccfffb6f01d13c9fb9680ebbf/activity_log.png?cb=138404ad7e0c149e97f5be6202ad7929) ## How to Access the Activity Log 1. Navigate tothe **Admin Panel**. 2. Go to the**Administration** section. 3. Select the**Activity Log** menu item. ## Parameters | **Parameter** | **Description** | |-------------------|---------------------------------------------------------------------------------------| | **Created At** | The timestamp when the action was recorded. | | **Administrator** | The administrator who performed the action. | | **IP Address** | The IP address from which the action was made. | | **Description** | A summary of the change or action performed. | | **Changes** | A detailed breakdown of the specific modifications made to an entity. | | **Filters** | Allows narrowing down logs based on Created At, Administrator, Section, or Entity ID. | --- language: "en" --- # Administration **Administration** is a set of configuration rules that prescribes how the system must be operated. ## Main functionality **Activity logs**---the section provides log details on actions performed by Administrators in the Admin Panel. For example, you can monitor internal activity such as transactions, profile creation, and account opening. **Administrators**---the functionality allows to see the list of Administrators and create new admin profiles. **Access Roles**---the functionality allows to create a set of actions permitted for a group of Administrators. **Access Groups**---the functionality allows to provide end users with access to the Admin Panel. For example, when a company accountant requires extended financial reports. **Authentication log**---the section shows the sign-in logs. **Authentication**---the section shows the list of all authentication attempts. **Legal documents**---the section allows to setup documents that should be accepted by end users; for example, Term and Conditions. **Transfer provider operation time**- setting up operation time of a transfer service provider. * [Access roles (Administration)](https://help.crassula.io/knowledge/access-roles-administration.md) * [Activity log](https://help.crassula.io/knowledge/activity-log.md) * [Administrators](https://help.crassula.io/knowledge/administrators.md) * [API Request log](https://help.crassula.io/knowledge/api-request-log.md) * [Authentication Log](https://help.crassula.io/knowledge/authentication-log.md) * [Country groups](https://help.crassula.io/knowledge/country-groups.md) * [Custom legal agreements](https://help.crassula.io/knowledge/custom-legal-agreements.md) * [Dictionary](https://help.crassula.io/knowledge/dictionary.md) * [Emergency shutdown](https://help.crassula.io/knowledge/emergency-shutdown.md) * [Invoices](https://help.crassula.io/knowledge/invoices.md) * [Legal Document Announcements](https://help.crassula.io/knowledge/legal-document-announcements.md) * [Legal documents](https://help.crassula.io/knowledge/legal-documents.md) * [Transfer provider operational time](https://help.crassula.io/knowledge/transfer-provider-operational-time.md) --- language: "en" --- # Administrative Panel The Administrative Panel as a back-end solution is your gateway to the diverse range of services offered by Crassula. This section provides in-depth insights into the various facets of our platform, from banking and card issuing to exchange, reports, and administration. Explore the multitude of capabilities that Crassula brings to the table to empower your financial operations. Each child page is dedicated to a specific domain, guiding you through the functionalities, processes, and benefits that Crassula's platform offers. Whether you're operating in banking, card issuance, exchange, or need robust administration tools, this section has you covered. * [Application](https://help.crassula.io/knowledge/application.md) * [Banking](https://help.crassula.io/knowledge/banking.md) * [Card Issuing](https://help.crassula.io/knowledge/card-issuing.md) * [Card Product](https://help.crassula.io/knowledge/card-product.md) * [Exchange](https://help.crassula.io/knowledge/exchange.md) * [Reports](https://help.crassula.io/knowledge/reports.md) * [Administration](https://help.crassula.io/knowledge/administration.md) * [Webhooks](https://help.crassula.io/knowledge/webhooks.md) See [Web and Mobile Interfaces](https://help.crassula.io/knowledge/web-and-mobile-interfaces.md) for Crassula front-end solutions. --- language: "en" --- # Administrators ## Overview **Administrator** is an administrative profile with access to the Admin Panel. The functionality varies depending on the administrative access roles assigned to the profile. The most common use case is managing clients and transactions within an Admin Panel section. For example, an Administrator can be responsible for the Banking section, while another one is entitled to manage only Exchange transactions. ### Related pages [Access roles (Administration)](#) [Agents](https://help.crassula.io/knowledge/agents.md) ## Opening the item Follow the steps below to access an Administrator profile: 1. Navigate to the Admin Panel 2. Click **Administration**on the left sidebar 3. Go to the **Administrators**menu item. 4. Click **Show** or **Edit**in a profile line to open its details. ## How to create an Administrator profile **To create an Administrative profile** 1. Navigate to the Admin Panel 2. Click **Administration**on the left sidebar 3. Go to the **Administrators**menu item. 4. Click **Add new** to create a profile. 5. Fill in the personal details fields, including the following: 1. **First name** , **Last name** , **Email** , and **Locale**. 2. Set the **Enabled** checkbox to activate the profile once it is created. 3. Set the profile password in the **Password** and Repeat password fields. The credentials will be used for logging in to the Admin Panel. 4. Select one or several access roles for the profile from the **Access Roles** drop-down list. See [Access roles (Administration)](https://help.crassula.io/knowledge/access-roles-administration.md) for functionality details. 5. Select a role from the **Role** drop-down list: 1. **Admin**: an Administrator with access limited by the defined access roles. 2. **Super Admin**: an Administrator with unlimited access within the Admin Panel. 3. **Agent**: a White label agent entitled to create new client profiles. 6. Click **Create** to confirm the profile creation. ![admin_create.png](https://help.crassula.io/__attachments/a_d237d99a671550be3cf95a6ce58fbca1426f1e2f6a10727b6ba363da2b8cd8e5/admin_create.png?cb=966c0ecb920921c1c230c81d13ac2aa0) ## Component parameters ![admins_list.png](https://help.crassula.io/__attachments/a_ba232d8ac8900de2ec7296c2a1e0c445d8236216e9ba20840ca876c233c7dff7/admins_list.png?cb=efe2482263f7494acb106c3e8008e9f8) | **Parameter** | **Description** | |--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Id** | The column demonstrates internal identification numbers assigned to Administrators. | | **First Name** | First name of an Administrator. | | **Last Name** | Last name of an Administrator. | | **Email** | Email address of an Administrator. The parameter value is used as credentials | | **Role** | Defines the type of an administrative profile: * **Admin** : an Administrator with limited access. This type of Administrator is mostly entitled to a specific functionality depending on the defined access roles. For example, an Administrator can access the Banking section, while the other sections remain unavailable. See [Access roles (Administration)](https://help.crassula.io/knowledge/access-roles-administration.md) for details. * **Super Admin**: an Administrator with unlimited access within the Admin Panel. Such Administrators can access any section of the Admin Panel and are entitled to create and edit Admin profiles. * **Agent** : a White label agent entitled to create new client profiles. See [Agents](https://help.crassula.io/knowledge/agents.md) for details. | | **Enabled** | Defines whether the profile is active and can be used to access the Admin Panel. | | **Is Two Factor Auth Enabled** | Defines whether the 2FA is enabled for the profile. | | **Action** | * Click **Show**to open profile details without the ability to edit them. * Click **Edit** to open profile details with the right to apply changes. | | **Help** | Click to access the current page right from the Admin Panel. | ## Configuring the component ![admin_details.png](https://help.crassula.io/__attachments/a_b8d0b3b81b12d090cdd31c5e74e6b0ee8b6dd34e6b8d37aaa9e165cbd3572648/admin_details.png?cb=c38799cd200226888b9dde4185daeb87) | **Parameter** | **Description** | |---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **First Name** | First name of an Administrator. | | **Last Name** | Last name of an Administrator. | | **Email** | Email address of an Administrator. The parameter value is used as credentials | | **Locale** | Defines the location and language for the profile. | | **Enabled** | Defines whether the profile is active and can be used to access the Admin Panel. | | **Password** | Profile password. The credentials will be used for logging in to the Admin Panel. Fill in the field with the new profile password when changing it | | **Repeat password** | Fill in the field with the new profile password when changing it. | | **Access roles** | Defines which access roles are assigned to the profile. Click the field and select an access role from the drop-down list. See [Access roles (Administration)](https://help.crassula.io/knowledge/access-roles-administration.md) for details. | | **Access groups** | Defines which administrative access groups are assigned to the profile. An Access group defines which objects will be available for an agent or an administrator in the Admin Panel. For example, you can define exact client profiles that will be visible to the Agent. If the field is not set, the agent will see all objects. | | **Role** | Defines the type of an administrative profile: * **Admin** : an Administrator with limited access. This type of Administrator is mostly entitled to a specific functionality depending on the defined access roles. For example, an Administrator can access the Banking section, while the other sections are not available to them. See [Access roles (Administration)](https://help.crassula.io/knowledge/access-roles-administration.md) for details. * **Super Admin**: an Administrator with unlimited access within the Admin Panel. Such Administrators can access any section of the Admin Panel and are entitled to create and edit Admin profiles. * **Agent**: a White label agent entitled to create new client profiles. See Agents for details. | --- language: "en" --- # Advanced Front-end Solutions Crassula offers additional enhancements that extend the functionality of Web and Mobile Interfaces, improving user experience and operational efficiency. These features provide configurable options that can be enabled to streamline processes and reduce manual interactions. * [Automatic Account Creation](https://help.crassula.io/knowledge/automatic-account-creation.md) * [Convert and Send](https://help.crassula.io/knowledge/convert-and-send.md) * [Supported Languages in Crassula Web and Mobile Interfaces](https://help.crassula.io/knowledge/supported-languages-in-crassula-web-and-mobile-int.md) --- language: "en" --- # Agents ## Overview **Agent** is an administrative role with restricted access. The main functionality of the role is managing client profiles via the Administrative panel for and on behalf of a White Label project. Agents are allowed to manage clients' profiles within an exact project. See the following scheme for example: ![agents.jpg](https://help.crassula.io/__attachments/a_50b9533844169550392121c214f97bad410dccc11cb6a76203b84c63f6293408/agents.jpg?cb=47a62819315c40bf4a9d2e884ce10143) ### Related pages [Access roles (Administration)](https://help.crassula.io/knowledge/access-roles-administration.md) [Administrators](https://crassula.atlassian.net/wiki/pages/resumedraft.action?draftId=1495072769) ## Opening the item Follow the steps below to access an Agent profile: 1. Navigate to the Admin Panel 2. Click **Administration**on the left sidebar 3. Go to the **Administrators**menu item. 4. Click **Filters** in the top right corner and select the **Role** option from the drop-down list. 5. Select **Agent** in the role field and click **Filter**. 6. Click **Show** or **Edit**in a profile line to open its details ## How to create an Agent profile Due to a dependency on a project, an Agent profile requires additional configuration to define which project it is related to. Thus, profile creation is performed as follows: 1. Create an API key. 2. Create an Agent profile and assign the API key to the Agent profile. Once all the actions are performed, the Agent will be able to log in to the Admin Panel and create new client profiles on behalf of the White Label (WL) project. **To create an API key** 1. Navigate to the Admin Panel. 2. Click **API**in the left sidebar. 3. Go to the **API keys**menu item. 4. Click **Add new** to create a new API key. 5. Set the WL project name in the **Client** field. The project must be registered as a [Company](https://help.crassula.io/knowledge/companies.md) in the Admin Panel 6. Fill the **Allowed IPs** field to specify the machine the Agent will use to log in. The field is optional. 7. Set the API key **Type** to define whether it is used for testing or production purposes. 8. Set the **Enabled** checkbox to activate the key once it is created. 9. It is also possible to define **Access roles** that can be used with the key. The field is optional. When creating an API key for Agents, it is recommended to leave the field empty and set an Access role within the Agent profile. However, it is important to create and add an **API key** [Access Role](https://help.crassula.io/knowledge/access-roles-administration.md) to have access via API. 10. Click **Create** to confirm the key creation. ![api_key_create.png](https://help.crassula.io/__attachments/a_4c0545b20fe0e4d6528870239482259f292421184af170254b4553fba664850b/api_key_create.png?cb=f62abef80c3b00b276a9f4bee43210ef) **To create an Agent profile** 1. Navigate to the Admin Panel. 2. Click **Administration**on the left sidebar. 3. Go to the **Administrators**menu item. 4. Click **Add new** to create a profile. 5. Fill in the personal details fields, including the following: 1. **First name**. 2. **Last name**. 3. **Email**. 4. **Locale**. 6. Set the **Enabled** checkbox to activate the profile once it is created. 7. Set the profile password in the **Password** and Repeat password fields. The credentials will be used for logging in to the Admin Panel. 8. Select an Agent access role for the profile from the **Access Roles** drop-down list. The number of access roles is limited for agents; see the following sections for the parameter description. 9. Select the **Agent** role from the **Role** drop-down list. 10. Select the API key from the **Agent companies** drop-down list. 11. Click **Create** to confirm the profile creation. ![agent_profile_edit.png](https://help.crassula.io/__attachments/a_1f394807de2e731d3a04317c2699d7b092fe759b9c1f72c460a6c1d6e4380a99/agent_profile_edit.png?cb=4a18734f642d7a85e73824ab56f6463d) ## Component parameters ![agents_list.png](https://help.crassula.io/__attachments/a_2925060b4c16f8550cebbf1751736543917e5c2cf3dff35b54f5e7fb7ef8b6a0/agents_list.png?cb=82bfc1dfb94a02803ac6ec04fa36fce0) | **Parameter** | **Description** | |--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Id** | The column demonstrates internal identification numbers assigned to Administrators. | | **First Name** | First name of an Administrator. | | **Last Name** | Last name of an Administrator. | | **Email** | Email address of an Administrator. The parameter value is used as credentials | | **Role** | Defines the type of an administrative profile: * **Admin** : an Administrator with limited access. Administrators of this type are mostly entitled to a specific functionality depending on the defined access roles. For example, an Administrator can access the Banking section, while the other sections remain unavailable. See [Access roles (Administration)](https://help.crassula.io/knowledge/access-roles-administration.md) for details. * **Super Admin**: an Administrator with unlimited access within the Admin Panel. Administrators of this type can access any section of the Admin Panel and are entitled to create and edit Admin profiles. * **Agent**: a project agent entitled to create new client profiles and manage existing ones. See Agents for details. | | **Enabled** | Defines whether the profile is active and can be used to access the Admin Panel. | | **Is Two Factor Auth Enabled** | Defines whether the 2FA is enabled for the profile. | | **Action** | * Click **Show** to browse profile details. * Click **Edit** to change profile details. | | **Help** | Click to access the [Administrators](https://help.crassula.io/knowledge/administrators.md) page right from the Admin Panel. | ## Configuring the component ![agent_profile_edit.png](https://help.crassula.io/__attachments/a_1f394807de2e731d3a04317c2699d7b092fe759b9c1f72c460a6c1d6e4380a99/agent_profile_edit.png?cb=4a18734f642d7a85e73824ab56f6463d) | **Parameter** | **Description** | |---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **First Name** | First name of an Administrator. | | **Last Name** | Last name of an Administrator. | | **Email** | Email address of an Administrator. The parameter value is used as credentials | | **Locale** | Defines the location and language for the profile. | | **Enabled** | Defines whether the profile is active and can be used to access the Admin Panel. | | **Password** | Profile password. The credentials will be used for logging in to the Admin Panel. Fill in the field with the new profile password when changing it | | **Repeat password** | Fill in the field with the new profile password when changing it. | | **Access roles** | Defines which access roles are assigned to the profile. Click the field and select an access role from the drop-down list. The agent will see the selected functionality in the Admin Panel only for the company to which they have access. See [Access roles (Administration)](https://help.crassula.io/knowledge/access-roles-administration.md) for additional details. Only the following actions can be included in an Agent access role: * *Persons: List, Create, Edit, Show, and Export.* * *Companies: List, Create, Edit, Show, and Export.* * *Company staff: List, Show, and Export.* * *Accounts: List, Show, and Export.* * *Transactions: List, Show, and Export.* * *Client Documents: All.* * *Identification Requests: All.* * *Expiring documents: All* All other actions are not assured. | | **Access groups** | Defines which administrative access groups are assigned to the profile. An Access group defines which objects will be available for the agent in the Admin Panel. For example, you can define exact client profiles that will be visible to the Agent. If the field is not set, the agent will see all objects. | | **Role** | Defines the type of an administrative profile: * **Admin** : an Administrator with limited access. Administrators of this type are mostly entitled to a specific functionality depending on the defined access roles. For example, an Administrator can access the Banking section, while the other sections are not available to them. See [Access roles (Administration)](https://help.crassula.io/knowledge/access-roles-administration.md) for details. * **Super Admin**: an Administrator with unlimited access within the Admin Panel. Administrators of this type can access any section of the Admin Panel and are entitled to create and edit Admin profiles. * **Agent**: a project agent entitled to create new client profiles and manage existing ones. See Agents for details. | | **Agent companies** | Defines the WL project name on behalf of which the Agent accesses the Admin Panel. The functionality is enabled in the **API keys** section. The parameter is inherited by client profiles opened by the Agent. | --- language: "en" --- # AML&KYC service providers The following article provides a brief overview of the service providers available for the AML\&KYC solutions. Navigate across the comparative table below to find the most relevant AML\&KYC solution: | | **Sumsub** | **NameScan** | **Payall** | **Salv** | **ComplyAdvantage** | **Unlimit** | | **Automated KYC \& KYB** | yes | no | no | no | no | no | | **AML onboarding module** | yes | no | yes | yes | no | no | | **Id checks** | yes | no | no | no | no | yes | | **Sanctions \& PEP screening, adverse media** | yes | yes | yes | yes | yes | no | | **Fiat transaction monitoring** | yes | no | no | yes | yes | no | | **Crytpo transaction monitoring** | yes | no | no | no | no | no | | **Crypto travel rule** | yes | no | no | no | no | no | |-----------------------------------------------|------------|--------------|------------|----------|---------------------|-------------| --- language: "en" --- # API Request log ## Overview **API Request log** comprehensively records all system-related API requests and offers detailed information for troubleshooting purposes. These logs reveal which resource initiated the request, quantify the associated load, and document the response sent in return. Advanced filtering options empower you to precisely locate a specific request by targeting its body content, ensuring efficient maintenance of the service level. ### Related pages [Banking API](https://docs.crassula.io/client) ## Opening the item Follow the steps below to access an API request: 1. Navigate to the Admin Panel 2. Click **Administration**on the left sidebar 3. Go to the **Api Request log**menu item. 4. Click **Show** in a request line to open its details. ## Component parameters ![API_list.png](https://help.crassula.io/__attachments/a_9d454c32b138b03b368756cbb5e54a46344382402d17f7a6ad0a6fb5e1dbb61c/API_list.png?cb=a5156e2f28df1c484baa5fff8997faca) | **Parameter** | **Description** | |-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Way** | Defines whether the request is incoming (green) or outgoing (yellow). | | **Requested At** | Date and time of request creation. | | **Initiator** | Request initiator details, such as API keys. | | **Uri** | Uniform Resource Identifier is a unique sequence of characters that identifies the resource of a request. | | **Method** | Defines the method used in a request. | | **User Agent** | Defines a webhook service used to generate a request. | | **Request Size** | Defines the amount of data in the request. | | **Response Size** | Defines the amount of data in the response. | | **Code** | Response code. | | **IP** | Request's IP address. | | **Action** | Click **Show**to open request details without the ability to edit them. | | **Filters** | * **Requested at**: Filter the list by date and time of request creation. * **Method**: Filter the list by request methods. * **Uri**: Filter the list by the resource identifier. * **Request body**: Filter the list by the contents of the request body. * **Response body**: Filter the list by the contents of the response body. * **Code**: Filter the list by response codes. | ## Configuring the component ![API_details.png](https://help.crassula.io/__attachments/a_527e717af9c4e4295c0356341d90ccce5276d0456f63e09d01a359db6bd2e074/API_details.png?cb=925cd68dd5a0e1f63c104196b18b3923) | **Parameter** | **Description** | |----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Way** | Defines whether the request is incoming (green) or outgoing (yellow). | | **Initiator** | Request initiator details, such as API keys. | | **Affected Objects** | If the request affects any object in the system---for example, personal details of a client---the **Change Log List** button is shown, which allows you to open **Client Activity logs** with the full list of affected objects. | | **Initiator** **Id** | Defines a unique sequence of characters that identifies the request Initiator. | | **Uri** | Uniform Resource Identifier is a unique sequence of characters that identifies the resource of a request. | | **Method** | Defines the method used in a request. | | **User Agent** | Defines a webhook service used to generate a request. | | **Code** | Response code. | | **IP** | Request's IP address. | | **Request Size** | Defines the amount of data in the request. | | **Response Size** | Defines the amount of data in the response. | | **Requested At** | Date and time of request creation. | | **Responded At** | Date and time of response creation. | | **Bodies** | Request and Response bodies. | --- language: "en" --- # API Request log \* ## Overview **API Request log** comprehensively records all system-related API requests and offers detailed information for troubleshooting purposes. These logs reveal which resource initiated the request, quantify the associated load, and document the response sent in return. Advanced filtering options empower you to precisely locate a specific request by targeting its body content, ensuring efficient maintenance of the service level. ### Related pages [Banking API](https://docs.crassula.io/client) ## Opening the item Follow the steps below to access an API request: 1. Navigate to the Admin Panel 2. Click **Administration**on the left sidebar 3. Go to the **Api Request log**menu item. 4. Click **Show** in a request line to open its details. ## Component parameters ![API_list.png](https://help.crassula.io/__attachments/a_9d454c32b138b03b368756cbb5e54a46344382402d17f7a6ad0a6fb5e1dbb61c/API_list.png?cb=a5156e2f28df1c484baa5fff8997faca) | **Parameter** | **Description** | |-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Way** | Defines whether the request is incoming (green) or outgoing (yellow). | | **Requested At** | Date and time of request creation. | | **Initiator** | Request initiator details, such as API keys. | | **Uri** | Uniform Resource Identifier is a unique sequence of characters that identifies the resource of a request. | | **Method** | Defines the method used in a request. | | **User Agent** | Defines a webhook service used to generate a request. | | **Request Size** | Defines the amount of data in the request. | | **Response Size** | Defines the amount of data in the response. | | **Code** | Response code. | | **IP** | Request's IP address. | | **Action** | Click **Show**to open request details without the ability to edit them. | | **Filters** | * **Requested at**: Filter the list by date and time of request creation. * **Method**: Filter the list by request methods. * **Uri**: Filter the list by the resource identifier. * **Request body**: Filter the list by the contents of the request body. * **Response body**: Filter the list by the contents of the response body. * **Code**: Filter the list by response codes. | ## Configuring the component ![API_details.png](https://help.crassula.io/__attachments/a_527e717af9c4e4295c0356341d90ccce5276d0456f63e09d01a359db6bd2e074/API_details.png?cb=925cd68dd5a0e1f63c104196b18b3923) | **Parameter** | **Description** | |----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Way** | Defines whether the request is incoming (green) or outgoing (yellow). | | **Initiator** | Request initiator details, such as API keys. | | **Affected Objects** | If the request affects any object in the system---for example, personal details of a client---the **Change Log List** button is shown, which allows you to open **Client Activity logs** with the full list of affected objects. | | **Initiator** **Id** | Defines a unique sequence of characters that identifies the request Initiator. | | **Uri** | Uniform Resource Identifier is a unique sequence of characters that identifies the resource of a request. | | **Method** | Defines the method used in a request. | | **User Agent** | Defines a webhook service used to generate a request. | | **Code** | Response code. | | **IP** | Request's IP address. | | **Request Size** | Defines the amount of data in the request. | | **Response Size** | Defines the amount of data in the response. | | **Requested At** | Date and time of request creation. | | **Responded At** | Date and time of response creation. | | **Bodies** | Request and Response bodies. | --- language: "en" --- # Application The functionality is under development and is subject to change. The Application section of the Administrative Panel is designed to include customization functionalities for frontend solutions, such as Web and Mobile Interfaces, to meet the needs of different clients and White Labels. * [Onboarding](https://help.crassula.io/knowledge/onboarding.md) --- language: "en" --- # Authentication Log ## Overview The **Authentication Log** tracks all authentication attempts across different system domains, including administrator and banking client logins. It also logs two-factor authentication (2FA) attempts, both successful and failed. This section provides a detailed log of authentication attempts, allowing administrators to monitor login activities, track failed login attempts, and identify potential security risks. The log includes key metadata, such as timestamps, IP addresses, user roles, and user agent details. ![Authentication_log.png](https://help.crassula.io/__attachments/a_7d79ab43c80da75034d03660734f3240234b2f8292d8a10cd6f9ef33fe886bb8/Authentication_log.png?cb=76d2dbce9c645e31d23e42e69b51179d) ## How to Access the Authentication Log 1. Navigate tothe **Admin Panel**. 2. Go to the**Administration** section. 3. Select the**Authentication Log** menu item. ## Parameters | **Parameter** | **Description** | |----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| | **Status** | Indicates whether the login attempt was successful or failed. Possible values include *Success login* , *Success two-factor* , and *Failure unknown*. | | **Domain** | Defines the platform where the authentication occurred. Options include *Administrator* and *Banking Client*. | | **Username** | The email address of the user attempting to log in. | | **IP Address** | The originating IP address of the authentication request. | | **Created At** | The timestamp of when the authentication attempt was initiated. | | **Updated At** | The timestamp of the latest status update for the authentication attempt. | | **Metadata** | Additional technical details about the login attempt, including API endpoints, referrer URLs, and browser user agent strings. | --- language: "en" --- # Authentication Log \* ## Overview The **Authentication Log** tracks all authentication attempts across different system domains, including administrator and banking client logins. It also logs two-factor authentication (2FA) attempts, both successful and failed. This section provides a detailed log of authentication attempts, allowing administrators to monitor login activities, track failed login attempts, and identify potential security risks. The log includes key metadata, such as timestamps, IP addresses, user roles, and user agent details. ![Authentication_log.png](https://help.crassula.io/__attachments/a_7d79ab43c80da75034d03660734f3240234b2f8292d8a10cd6f9ef33fe886bb8/Authentication_log.png?cb=76d2dbce9c645e31d23e42e69b51179d) ## How to Access the Authentication Log 1. Navigate tothe **Admin Panel**. 2. Go to the**Administration** section. 3. Select the**Authentication Log** menu item. ## Parameters | **Parameter** | **Description** | |----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| | **Status** | Indicates whether the login attempt was successful or failed. Possible values include *Success login* , *Success two-factor* , and *Failure unknown*. | | **Domain** | Defines the platform where the authentication occurred. Options include *Administrator* and *Banking Client*. | | **Username** | The email address of the user attempting to log in. | | **IP Address** | The originating IP address of the authentication request. | | **Created At** | The timestamp of when the authentication attempt was initiated. | | **Updated At** | The timestamp of the latest status update for the authentication attempt. | | **Metadata** | Additional technical details about the login attempt, including API endpoints, referrer URLs, and browser user agent strings. | --- language: "en" --- # Automatic Account Creation The functionality is not enabled by default. Contact your manager for configuration details. ## Overview Crassula's currency exchange process includes simplified account creation, enabling users to complete exchange transactions seamlessly by creating missing target currency accounts. This feature removes the need for manual account setup, making the exchange experience smoother and more efficient. ## Feature Highlights * **Streamlined Currency Exchange**: Allows to generate accounts in the required target currency, enabling exchanges that would otherwise be blocked. * **Integrated Account Creation**: Adds accounts directly within the exchange flow, eliminating interruptions. * **Prefilled Target Currency**: The target currency field is prefilled, simplifying the account setup process. * **Real-Time Validation**: Validates account details instantly to ensure accuracy. * **Error Handling**: Provides clear notifications if account creation fails, with support contact options. * **Automatic Redirection**: Returns users to the exchange screen with all transaction details prefilled. ![1.gif](https://help.crassula.io/__attachments/a_716047f61848541af0493e2aa593259c1a564a8f2d993ecba3788bed4088263f/1.gif) ## How It Works 1. **Initiate Exchange**: Start a currency exchange as usual. The system displays an error message if it identifies a missing target currency account. 2. **Open Account Prompt**: A popup prompts users to create a new target currency account. 3. **Account Creation**: * Enter an account name. * Confirm the prefilled target currency or choose another if permitted. 4. **Validation**: The system checks the entered details for accuracy before proceeding. 5. **Success/Error Feedback**: * **Success**: Displays "Account created!" and moves to the next step. * **Failure**: Shows an error message and provides support contact options. 6. **Return to Exchange**: Users are redirected back to the exchange screen with all previous details retained, and they are ready to proceed with the transaction. --- language: "en" --- # Banking **Core Banking** is one of the key Crassula products delivered as a ready-to-go solution. It includes everything necessary for digital banking to successfully function. ## Main functionality **Clients:** Every banking service requires a system to add new clients, edit their profiles, and provide them with online support if necessary. See [Persons](https://help.crassula.io/knowledge/persons.md) and [Companies](https://help.crassula.io/knowledge/companies.md) for solution details. **Accounts:** The Core Banking product provides your Clients with an unlimited amount of fully functioning accounts in various currencies and cryptocurrencies. See [Accounts](https://help.crassula.io/knowledge/accounts.md) for details. **Transactions execution** : Transactions are executed according to our API solution with the help of external service providers. See [Transactions](https://help.crassula.io/knowledge/transactions.md) to learn how to monitor and confirm transactions. **Fees:** One of the main sources of income for digital banking. See [Price lists](https://help.crassula.io/knowledge/price-lists.md) to learn how to set a price list for transactions. **Limitations:** Digital banking must follow the rules set by legal authorities. See [Limits](https://help.crassula.io/knowledge/limits.md) to learn more on limitations that could be set for Clients. **KYC/KYB/AML** : Digital banking must also follow the rules set by legal authorities when adding new clients to the client base and executing transactions. The required financial monitoring is delivered by external service providers. See [Identification requests](https://help.crassula.io/knowledge/identification-requests.md) to learn the details. **Banking** : Provides a detailed overview of how to operate a Digital Banking and the Administrative Panel itself. It is recommended to start with the [First Steps in the Admin Panel](https://help.crassula.io/knowledge/first-steps-in-the-admin-panel.md) before navigating to the child pages of this section. See the functional scheme below for **Core Banking** processing details. ![Banking_scheme.jpg](https://help.crassula.io/__attachments/a_864b9c8ec6b20672e73af01d481df3cf90ac28d445c8297a30adedd7436aef67/Banking_scheme.jpg?cb=19e369d97e16093af29fb25fcfeadbc1) *** ** * ** *** * [Access roles](https://help.crassula.io/knowledge/access-roles.md) * [Accounts](https://help.crassula.io/knowledge/accounts.md) * [Client application forms](https://help.crassula.io/knowledge/client-application-forms.md) * [Companies](https://help.crassula.io/knowledge/companies.md) * [Company staff](https://help.crassula.io/knowledge/company-staff.md) * [Crypto withdrawal limits](https://help.crassula.io/knowledge/crypto-withdrawal-limits.md) * [Expiring documents](https://help.crassula.io/knowledge/expiring-documents.md) * [Identification requests](https://help.crassula.io/knowledge/identification-requests.md) * [Limits](https://help.crassula.io/knowledge/limits.md) * [Persons](https://help.crassula.io/knowledge/persons.md) * [PEP\&Sanctions](https://help.crassula.io/knowledge/pep-sanctions.md) * [Price lists](https://help.crassula.io/knowledge/price-lists.md) * [Transactions](https://help.crassula.io/knowledge/transactions.md) * [Transactions (action required)](https://help.crassula.io/knowledge/transactions-action-required.md) * [Transactions (pre-approval)](https://help.crassula.io/knowledge/transactions-pre-approval.md) * [Triggered limits](https://help.crassula.io/knowledge/triggered-limits.md) * [Vaults](https://help.crassula.io/knowledge/vaults.md) * [Issues](https://help.crassula.io/knowledge/issues.md) --- language: "en" --- # Banking Mobile Interface **Banking Mobile Interface** is a mobile app that provides access to essential Banking services, starting from account opening and ending in exchanging cryptocurrencies. The following guide leads the user through the basics of **Banking Mobile Interface** and provides instructions on the actions available. The app is available for iOS and Android devices, while the guide demonstrates the iOS version. *The* ***Mobile Interface*** *design varies depending on the visual solutions of the White Label providing the service. Nevertheless, the interface structure and functionality are implemented according to the following guide.* * [Accounts (Mobile Interface)](https://help.crassula.io/knowledge/accounts-mobile-interface.md) * [Batch payments (Mobile Interface)](https://help.crassula.io/knowledge/batch-payments-mobile-interface.md) * [Cards (Mobile Interface)](https://help.crassula.io/knowledge/cards-mobile-interface.md) * [Currency exchange (Mobile Interface)](https://help.crassula.io/knowledge/currency-exchange-mobile-interface.md) * [Payments (Mobile Interface)](https://help.crassula.io/knowledge/payments-mobile-interface.md) * [Savings (Mobile Interface)](https://help.crassula.io/knowledge/savings-mobile-interface.md) * [Top-up (Mobile Interface)](https://help.crassula.io/knowledge/top-up-mobile-interface.md) ## Overview The Mobile Interface consists of several functionality fields that provide quick access to all the necessary details of your accounts in \. See the image below to navigate across the interface: 1. The **Account** tab provides the details on all accounts opened by the user and defines the default account. Every time you select an account from the list and access its details, the account is considered to be default and is shown on the Home page. 2. The default currency used to calculate total amounts. 3. The Balance field demonstrates the sum of funds on the default account. 4. The Quick Access field includes the most frequently used actions: topping up, currency exchange, savings, and default account details. 5. The Transaction History demonstrates recent transactions in the default account, including transfers, fees, and card transactions. 6. The Navigation sidebar is the main navigation instrument to switch between Mobile Interface functionalities. ![dashboard.jpg](https://help.crassula.io/__attachments/a_39b5de955d640342a0e505270eda63b39e494b93715cd836e1865e25239f911e/dashboard.jpg?cb=3cffb924f4a1ac79f737084f01e901dd) ## Signing up An existing profile is required to have access to all the Mobile Interface functions. Follow the steps below if you have not registered yet: 1. Open the \ app. 2. Click **Sign Up** to start creating your profile. 3. Fill in your email and set a password, and click **Next**. 4. Fill in your personal details and click **Continue**. 5. Acquaint yourself with the Terms and Conditions and confirm them by enabling the corresponding tumbler. 6. Click **Create account**. 7. Your profile is successfully created, and the Primary account is opened automatically. 8. Check your email for the identification link provided by the service. Follow the instructions to verify your email address. 9. Once your email is verified, you will be navigated to a phone verification link. Enter the verification code sent to your phone to verify your contacts. 10. Navigate to the document verification page to upload an ID document. 11. Complete the questionnaire (optional). 12. Wait for the document approval (takes up to several minutes). 13. Once the document approval is complete, the primary account is activated. 14. Navigate back to the \ app to log in using the newly created credentials. ![sign_up_1.jpg](https://help.crassula.io/__attachments/a_f9397db9dfe894b7e7b2c03de97930b6c87230dfc162ae3ed77a8cc32baa46f2/sign_up_1.jpg?cb=07e4ffd521149d4d0945028254e8036d) Signing up ## Signing in **To sign in for the first time** 1. Open the \ app. 2. Fill in your credentials for authorization. 3. Set a passcode to access the app. 4. Enable biometric authorization. It is also possible to do it later in the **Security**section. 5. The Mobile Interface will be opened. 6. All further authorizations will require only your passcode or biometrics unless you log out of the app. **To recover your password** 1. Click **Forgot Password?** below the Sign-inform. The password recovery window will be opened. 2. Enter your email address and click **Reset**. 3. The password recovery email will be sent to your email. Follow the instructions to reset your password. 4. Navigate back to the \ app and log in using the updated credentials. ![sign_in_1.jpg](https://help.crassula.io/__attachments/a_993ee24082ea546b4222530a4525ffc4c8198b8ef8b7345f41fe5b85d575cf54/sign_in_1.jpg?cb=f4bbc0cbbd8b8caf2dee1a925a125d36) Signing in ## Settings Navigate to the **More** tab in the Navigation bar to manage your profile details. |-----------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| | ![settings.jpg](https://help.crassula.io/__attachments/a_6fd9f6875b078c2b15ce9bc8652c2093e0aba845e14b13641d7d8f1c19cf7532/settings.jpg?cb=99ffced0cd1d1e76197f81281040dd3d) | ![settings_2.jpg](https://help.crassula.io/__attachments/a_85961c84b2fc176057d67da0cf27f40ba9b2286b96e1fc104223a44414e7ff23/settings_2.jpg?cb=1a97fa3cba3b16d3d0f5f478466deb19) | ### Profile The **Profile**section provides general information on your profile, including the following: * **Personal details**: Edit your address, though all the new information is to be verified by additional documents. * **Contact information**: Edit your contact details, though all the new information is to be verified. * **Username**: Set a username to receive funds using internal transfers without revealing your account number. * **Subscription plan**: Upgrade and downgrade your subscription to manage pricing rules for the banking service. * **Documents**(optional): Import your documents, send them for verification, and access the previously uploaded documents. * **Fees**(optional): Access the pricing rules applied to your profile if available. ### Security The**Security** sectionprovides a convenient way to set additional means of your profile protection: * **Change passcode**: Change your profile passcode. The current passcode is required. * **Sign in with Touch/Face ID:** Click the tumbler to turn on/off biometric authorization. * **2-step Verification**: Enable additional means of profile protection that include the following (only active clients can change their 2FA details): * **Text message**: Confirm app activity using codes sent as text messages to your mobile phone. * **Authenticator app** : Confirm app activity using either **Google Authenticator** or **Authy**. * **Change password**: change your profile password. The current password is required. ### About us The**About us** field provides links to \ social media. Subscribe not to miss new features. ### Legal The **Legal**section provides the following: * \ legal documents. * Support center. --- language: "en" --- # Banking Reports The section includes several reports that provide detailed information on White Label Banking, such as the following: 1. **Accounting report**: The report provides information about client accounts, including balances, incomes, fees charged from the accounts, and other details. 2. **Currency turnover report**: The report provides information about the volume and value of currency transactions processed by the White Label over a specific period. 3. **Fees report**: The report provides details on the fees charged by White Label to its clients over a specified period. The report includes information such as the type of fee, service providers, and the amount charged. 4. **Charged fees report**: The report provides details on the markup or spread charged by the bank on foreign currency exchange transactions. The report includes information such as the currency pair, the date of the transaction, the exchange rate, and the markup charged. * [Accounting (Banking reports)](https://help.crassula.io/knowledge/accounting-banking-reports.md) * [Charged Fees (Banking reports)](https://help.crassula.io/knowledge/charged-fees-banking-reports.md) * [Currency turnover](https://help.crassula.io/knowledge/currency-turnover.md) * [Fees](https://help.crassula.io/knowledge/fees.md) * [Historical Transactions Accounting](https://help.crassula.io/knowledge/historical-transactions-accounting.md) --- language: "en" --- # Banking service providers This section provides an overview of service providers available for the Core Banking solution. Below is a summary table of all Banking service providers with detailed information on the supported functionality: Click here to expand the table | **Provider Feature** | ++**Clear.Bank UK**++ | ++**Clear.Bank EU**++ | ++**Railsr**++ | ++**Clearjunction**++ | ++**Currencycloud**++ | ++**Centrolink (BoL)**++ ++**"litas-sepa"**++ | ++**Equals Money**++ | ++**IFX**++ | ++**Unlimit**++ | ++**B4B**++ | ++**Modulr**++ | ++**Zand**++ | | **Physical (Real) accounts** | yes | yes | yes | no | yes | no | yes | yes | yes | no | yes | yes | | **Virtual accounts** | yes | yes | no | yes | n/a | yes | no | yes | n/a | yes | n/a | yes | | **IBAN generation** | yes | yes | yes | yes | yes | yes | yes | yes | yes | no | yes | yes | | **Private accounts** | yes | yes | yes | yes | yes | yes | yes | yes | yes | n/a | yes | yes | | **Business accounts** | yes | yes | yes | yes | yes | yes | yes | yes | n/a | yes | yes | yes | | **Multi-currency accounts** | yes | yes | n/a | yes | yes | n/a | yes | yes | n/a | no | n/a | n/a | | **Mono-currency accounts** | yes | no | yes | yes | n/a | yes | n/a | yes | yes | yes | yes | yes | | **SEPA Credit Transfer (SCT)** | yes, incoming | yes | yes | yes | yes | yes | yes | yes, incoming only | yes | no | yes | n/a | | **SEPA Instant (EUR-3)** | n/a | yes | yes | yes | no | yes | no | n/a | n/a | n/a | yes | n/a | | **Target2 (EUR-1)** | yes, inbound | yes | no | n/a | no | no | no | n/a | n/a | n/a | n/a | n/a | | **SWIFT** | yes | n/a | yes | yes | yes | n/a | yes | yes | yes | yes | n/a | yes | | **Direct Debit (BACS, SEPA)** | yes | n/a | yes | n/a | n/a | no | n/a | n/a | n/a | n/a | TBD | n/a | | **CHAPS (UK)** | yes | n/a | yes | yes | yes | n/a | yes | n/a | n/a | no | no | n/a | | **Faster Payments (UK)** | yes | n/a | yes | yes | yes | n/a | yes | yes | n/a | no | yes | n/a | | **BACS (UK), incoming only** | yes | n/a | yes | no | no | n/a | no | n/a | n/a | no | no | n/a | | **ACH** | n/a | n/a | no | n/a | yes | n/a | n/a | n/a | n/a | no | n/a | n/a | | **Fedwire** | yes, inbound | n/a | n/a | yes | no | n/a | n/a | n/a | n/a | no | n/a | n/a | | **Intraday Payment (DKK)** | n/a | n/a | n/a | n/a | no | n/a | n/a | n/a | n/a | yes | n/a | n/a | | **FX orders + rates** | yes | no | no | yes | yes | n/a | no | no | n/a | no | n/a | n/a | | **Interledger** | yes | yes | yes | yes | yes | n/a | yes | yes | yes | n/a | yes | n/a | | **Refunds (incoming, outgoing)** | yes | yes | yes | yes | no | yes | no | no | n/a | no | yes | no | | **Bank transfer** | yes | yes | yes | yes | yes | no | yes | yes | yes | yes | yes | yes | | **CoP** | yes | n/a | no | yes | no | n/a | yes | n/a | n/a | no | TBD | no | | **Provider Dashboard** | yes | no | no | yes | no | yes | yes | yes | yes | yes | yes | no | |----------------------------------|-----------------------|-----------------------|----------------|-----------------------|-----------------------|-----------------------------------------------|----------------------|--------------------|-----------------|-------------|----------------|--------------| --- language: "en" --- # Banking Web Interface **Banking Web Interface** is a visualization instrument that provides access to all the necessary Banking services, starting from account opening and ending in exchanging cryptocurrencies. The following guide leads the user through the essentials of **Banking Web Interface** and provides instructions on the actions available. The **Web Interface** design varies depending on the visual solutions of the White Label providing the service. Nevertheless, the interface structure and functionality are implemented according to the following guide. * [Accounts (Web Interface)](https://help.crassula.io/knowledge/accounts-web-interface.md) * [Batch payments (Web Interface)](https://help.crassula.io/knowledge/batch-payments-web-interface.md) * [Cards (Web Interface)](https://help.crassula.io/knowledge/cards-web-interface.md) * [Currency exchange (Web Interface)](https://help.crassula.io/knowledge/currency-exchange-web-interface.md) * [Payments and transfers (Web Interface)](https://help.crassula.io/knowledge/payments-and-transfers-web-interface.md) * [Savings (Web Interface)](https://help.crassula.io/knowledge/savings-web-interface.md) * [Top-up (Web Interface)](https://help.crassula.io/knowledge/top-up-web-interface.md) ## Overview The Web Interface consists of several functionality fields that provide quick access to all the necessary details of your accounts in \. See the image below to navigate across the interface: 1. The Navigation sidebar is the main navigation instrument to switch between the **Web Interface** functionalities. 2. The Quick Access field includes the most frequently used actions -- opening a new account, topping up, and transfers. 3. The Total balance field demonstrates the sum of funds from all the opened accounts. 4. Primary account details and the linked cards. 5. Recent currency exchange orders. 6. Transaction history demonstrates recent transactions including transfers, fees, and card transactions. 7. Profile option allows to switch between personal and business profiles without signing out of the **Web Interface**. ![overview.png](https://help.crassula.io/__attachments/a_f2b33b64453187cdd367fb1403b56de1703e186a7862ca0a38295fe774795ee7/overview.png?cb=bfa51872a03c0431b74fc737d2780233) ## Signing up An existing profile is required to have access to all the Web Interface functions. Follow the steps below if you have not registered yet: 1. Navigate to [\](https://client.crassula.io/sign-in/). 2. Click **Sign Up** below the form to start creating your profile. A page with profile types will be opened. 3. Click **Create** to open a Private account. The Sign-Up form will be opened. 4. Fill in your personal details and acquaint yourself with the terms of use provided below. 5. Click **Create Account** to submit the form. 6. Your profile is successfully created and the Primary account is opened automatically. 7. Check your email for the identification link provided by the service. Follow the instructions to verify your email address. 8. Once your email is verified you will be navigated to a phone verification link. Enter the verification code sent to your phone to verify your contacts. 9. Navigate to the document verification page using one of the following methods: 1. A link for document upload. 2. A QR-code for online video verification. 10. Complete the questionnaire (optional). 11. Wait for the document approval (takes up to several minutes). 12. Once the document approval is complete, the primary account is activated. 13. Navigate back to the Sign-in page to log in using the newly created credentials. *It is possible to Sign in to the* ***Web Interface*** *before completing the identification process, though such actions as transfers, currency exchange, and card issuing will be restricted.* ![sign_up_1.png](https://help.crassula.io/__attachments/a_a5b72fe2330c44e95dd9e5d70ccba7a6a222c7539e2afa27d77124ad4951b0a8/sign_up_1.png?cb=dce36f35faa1472cc8b33278b4de1b46) ![sign_up_2.png](https://help.crassula.io/__attachments/a_c0032c04425f47a216b53f4750528f488ffaa3e34e742808f00683372932bb47/sign_up_2.png?cb=5ad662486c840b3ed53060b38f2780cf) ## Signing in If you already have an account, follow the steps below to sign in: 1. Navigate to [\](https://client.crassula.io/sign-in/) . 2. Fill in your credentials for authorization. 3. The **Web Interface** will be opened ![sign_in.png](https://help.crassula.io/__attachments/a_31c704a3aeaf8c9b47bfcf1016aaf8c88fbd910b794e971cf141b064611526ba/sign_in.png?cb=0f5b347358f77f3d21482fe5bf3ff654) If you forgot your password, the recovery process is executed as follows: 1. Click **Recover** below the Sign-inform. The password recovery window will be opened. 2. Enter your email address and click **Reset**. 3. The password recovery email will be sent to your email - follow the instructions to reset your password. 4. Navigate back to the Sign-in page and log in using the updated credentials. ![password_recovery.png](https://help.crassula.io/__attachments/a_58bc15dd9cab683afa6168b7332ae5d86222410af17c30a5bc35433d9b463cbd/password_recovery.png?cb=67eeaedc27a29a0eb92cb6c9199272dd) ## Settings Navigate to **Settings** in the top sidebar to manage your personal details. ### Profile The **Profile** tab provides general information on your profile. * **Personal details**: the field defines general personal details. It is possible to edit the details, though all the new information is to be verified by additional documents. * **Username** : the username can be used instead of account details to transfer funds inside the \. * **Language:** the field defines the interface localization languages available in the \. * **Contact information**: the field defines main contact details. It is possible to edit the details, though all the new information is to be verified by additional documents. * **Client tier** : the field shows current tier level. When provided by the \, you can upgrade/downgrade your tier level for an extra charge to change your profile limits and rates. * **Cashback**: the field shows all active cashback reward programs that are applied to your outgoing transfers. * **Fees**: the field shows all active fees that are applied to your transfers and other transactions. ![settings.png](https://help.crassula.io/__attachments/a_82d5f07f028bbd47416dee9cc396fe6bc155f4b367878f9e8fce21ac8dbaae87/settings.png?cb=2260a764a7febcf06674a2e968aef441) **To upgrade your tier level** 1. Navigate to the **Client Tier** field of the profile settings. 2. Click **Upgrade** in the corresponding tier line. 3. The payment widget will be opened. 4. Set an account for payment processing. 5. Set a currency for multi-currency accounts. 6. Click **Get \** to confirm the upgrade. ![tier_upgrade.png](https://help.crassula.io/__attachments/a_c96a0bca71f8908a747a4c5ba68001007b10e04ed52fd2252a1e9331f1c2a785/tier_upgrade.png?cb=d39471ad8f20da3baa3966890e5f6bf1) ### Documents The**Documents** tabprovides a convenient way to upload a new document if one is requested by the compliance and support teams. Click **Choose a file** to upload a document. ![documents.png](https://help.crassula.io/__attachments/a_fb62597dd4cbd057b9f8c29a081276be5f34d8ac1b10a7cf8fe45f33e0cf81d3/documents.png?cb=4c8575c9ad6b24bca41920fa1a7a77cf) ### Security Currently, the Security section is available only for Persons. The**Security** sectionprovides a convenient way to set additional means of your profile protection: * **2-step Verification** is an additional functionality of profile protection (only active clients can change their 2FA details): * Text message - confirm app activity using codes sent as text messages to your mobile phone. * Authenticator app - confirm app activity using either **Google Authenticator** or **Authy**. * **Change password**- change your profile password. A currently active password is required. ![security.png](https://help.crassula.io/__attachments/a_be02ff0f5a81eec13bda9459f753d9caecf9d25eb63664e04738dca015e74825/security.png?cb=1d515b90eee9a13df12c3f81b8d19d92) ### Invite a friend This section allows clients to share their referral codes with friends to join the financial service. Both the referrer and the referral can earn rewards on eligible transactions, fostering a seamless and rewarding referral experience. See [Referral program](https://help.crassula.io/knowledge/referral-codes.md) for additional details on the functionality. ![invite_a_friend.png](https://help.crassula.io/__attachments/a_30450e9db78057065577677420f9528a92df842d5d4d80bc28f80a114c55bfff/invite_a_friend.png?cb=e16fa400cbfeb6ac64e34106feb8d010) --- language: "en" --- # Batch payments (Mobile Interface) ## Creation of a new batch payment To create a batch payment, follow the steps below: 1. In the Mobile Interface, navigate to the **Payments \> Batch** tab. ![batch_payments.png](https://help.crassula.io/__attachments/a_ad5c8210bae45f78e77287aa88a9b4e9837a257cb95bb69a020d5cd1ecf7ef7e/batch_payments.png?cb=98ea7b88b2cf55daee1cca4256958f78) 2. Click **Add new**. 3. On the **Upload Batch** screen, select an account from the list of available accounts and a payment method that is supported by the selected account. 4. Click Add a file to import the list of payments. See the [CSV template details](https://help.crassula.io/knowledge/fiat-batch-payments#Fiatbatchpayments-CSVtemplatedetails) subsection for additional details on the file fields. 5. Click the **Upload** **batch**button to complete the uploading. A dialog confirming that the file has been uploaded successfully will appear. ![batch_payments_2.png](https://help.crassula.io/__attachments/a_56850d3971634f17d03127df2d4a6e6737fa133cbf67f55d6627b9630bc64dbb/batch_payments_2.png?cb=aa4dad00a523f8005974c3e0bb52831e) As a result, the batch payment will appear in the list on the **Batch**tab. All newly created batch payments have the Waiting for approval status. For more information on statuses, see the [Checking the status of a batch payment](https://help.crassula.io/knowledge/fiat-batch-payments#Fiatbatchpayments-Checkingthestatusofabatchpayment) subsection. --- language: "en" --- # Batch payments (Web Interface) ## Creation of a new batch payment To create a batch payment, follow the steps below: 1. In the Web Interface, navigate to the **Payments \& transfers** \>**Batch** section. ![image-20230726-232039.png](https://help.crassula.io/__attachments/a_cfeafc64e2b5796e64b0b25ee79b38a092df8cba6b4f6cbc573d2838f98658b2/image-20230726-232039.png?cb=b5665137ad83a3d09f3f099bdd963cf6) 2. Click the **Add new** tab. 3. On the **Upload Batch** screen, select an account from the list of available accounts and a payment method that is supported by the selected account. Selecting both is mandatory; otherwise, you won't be able to proceed with the next step. ![image-20230726-232236.png](https://help.crassula.io/__attachments/a_a68222674f92fe6148a2f945a7681b7fd0c4e968a63deefa3b197310cf9387a6/image-20230726-232236.png?cb=c1b3e457b053f82a09f5f19fa56be2e5) 4. Click **Download .csv template** to download the CSV file on your machine. The template contains all the necessary fields that you need to fill in to perform the payment. For more information on the template, see the [CSV template details](https://help.crassula.io/knowledge/fiat-batch-payments#Fiatbatchpayments-CSVtemplatedetails) subsection. 5. On your machine, fill in the payment information for every individual transaction in the corresponding fields of the template and save the changes. Rename the CSV file if necessary. 6. Once you've filled in all the payment information, navigate back to the **Upload Batch** screen and either click **Select .csv file to upload** or simply drag and drop the file in the upload box. The file will appear as a separate item under the upload box. 7. Click the **Upload** button to complete the uploading of a template. A dialog confirming that files have been uploaded successfully will appear. As a result, the batch payment will appear in the table on the All tab. All newly created batch payments have the Waiting for approval status. ![image-20230726-232731.png](https://help.crassula.io/__attachments/a_1fd3e7ddf6dc2e705ae7bf8957538b32182017cade55436524b1620d5018afc8/image-20230726-232731.png?cb=d59721f0f7838063a234991ea4eb9c26) For more information on statuses, see the [Checking the status of a batch payment](https://help.crassula.io/knowledge/fiat-batch-payments#Fiatbatchpayments-Checkingthestatusofabatchpayment) subsection. ### Approving a batch payment To approve a batch payment, follow these steps: 1. In the Web Interface, navigate to the **Payments \& transfers \> Batch** section. 2. In the table on the **All** tab, click the **Details** button of the batch payment that you want to approve. 3. On the screen that appears with all the separate payments included in the batch payment, perform one of the following actions: * To approve a batch payment, click **Approve** . The batch payment will have the *Processing* status. * To decline a batch payment, click **Decline** . The batch payment will have the *Rejected* status. When the approved batch payment is completed, it will change its status from Processing to Completed. Once it's completed, you can see all payments included in the batch as separate transactions in the **Dashboard**. Please note that a batch will have the **Completed** status even though some of its transactions were declined while processing. For instance, after approving a batch, if 99 transactions out of 100 are successfully processed, while 1 transaction is declined, the status of the batch payment will be **Completed** . The same rule applies to situations with insufficient funds in the account: Transactions will be carried out until the funds run out, and the remaining transactions will not be processed, while the batch payment will have the **Completed** status. For more information on statuses, see the [Checking the status of a batch payment](https://help.crassula.io/knowledge/fiat-batch-payments#Fiatbatchpayments-Checkingthestatusofabatchpayment) subsection. --- language: "en" --- # Card Issuing **Card Issuing** is an additional Crassula product that is mostly used in combination with Core Banking. It provides the necessary API solutions to issue fully functioning virtual and plastic cards for Clients. All cards are issued by service providers -- the White label only requires transaction monitoring and clearing. ## Main functionality **Cards issued by Clients** - See [Issued cards](https://help.crassula.io/knowledge/issued-cards.md) to monitor all cards issued by your Clients. **Card transactions** - the list of transactions is delivered by a service provider for monitoring and confirmation if one is necessary. See [Issued card holds](https://help.crassula.io/knowledge/issued-card-holds.md) and [Issued card transactions](https://help.crassula.io/knowledge/issued-card-transactions.md) for details. **Clearing** is the main source of information when cards get declined. See [Clearing process log](https://help.crassula.io/knowledge/clearing-process-log.md) and [Issued card failed auth](https://help.crassula.io/knowledge/issued-card-failed-auth.md) to learn how to monitor the transactions processing information. The **Card issuing**section of the Knowledge base provides an overview of how to operate a card issuing service and the Administrative Panel itself. Navigate to the child pages of this section to learn the process. * [Clearing process log](https://help.crassula.io/knowledge/clearing-process-log.md) * [Issued cards](https://help.crassula.io/knowledge/issued-cards.md) * [Issued card failed auth](https://help.crassula.io/knowledge/issued-card-failed-auth.md) * [Issued card holds](https://help.crassula.io/knowledge/issued-card-holds.md) * [Issued card transactions](https://help.crassula.io/knowledge/issued-card-transactions.md) [Next Page](https://help.crassula.io/llms-full.txt/1)