Back Office Guide¶

Getting started¶

Authorization and permissions¶

To get access to the Back Office you need an active profile in the system. Use login and password, provided by the administrator to log in the system.

In case of error, check login and password correctness, input language, Caps Lock key. If everything seems to be correct, contact the administrator to check the status of your profile.

Note

Access to different parts and/or functions of the Back Office depends on your permissions.

Your permissions depend on the user group you’re included in.

General interface options¶

All screens of the Back Office interface are designed similarly and most of them provide common functions, such as data exporting, visibility settings, and so on, which will be covered in more detail in the following sections.

Here are some general notes on the interface options, which are available in the topbar on all screens:

click the burger button to expand/collapse the main menu,
click the shield icon to see antifraud notifications, counter badge on the icon shows the number of new notifications,
click the bell icon to see pending clients requests, counter badge on the icon shows the number of new requests,
click the language icon to select language,
click your login to see the log out button.

Buttons below always have the same functions throughout the interface:

— search button is located in table header and used to apply filters,
— reset button is located in table header and used to reset applied filters,
— edit button is located in table row and used to switch to detailed view of the content,
— delete button is located in table row and used to delete this row content,
— create button is located above the table and used to add a new entry,
— export button is located above table and used to export table content to a CSV file.

Some content of the pages (like ID or name) are hyperlinks, which lead you to the details page, if you have required permissions.

Filters and sorting¶

As data in the Back Office subsections is organized in tables, you may sort and filter its content.

If sorting by the parameter is available, you’ll see arrows near the column header:

inactive arrows (gray): sorting by this parameter is disabled,
active up arrow: ascending sorting,
active down arrow: descending sorting.

Note

Sorting by only one parameter can be applied at a time.

If search filters are available, you’ll see input fields under the column header. Type of input depends on the column content: it can be text, number, date, selector, etc. For filtering by date usually two fields are available: start date and end date, so that you can specify a period.

To enable filtering, click the search button. To cancel filtering, click the reset button.

Note

Several filters can be applied at a time. You can also sort filtered data.

Pagination¶

You can specify number of rows in a table by selecting the number of records to be displayed.

You can directly specify the page to be displayed or use left/right arrows to navigate to previous/next page.

Visibility settings¶

You can choose which data you want to display in the table: click Visibility Settings and mark/unmark the columns you’d like to display/hide.

Note

Visibility settings will be changed for all the users of the Back Office.

Data export¶

Almost all pages of the Back Office support data export to CSV. Generated file can be either downloaded to your computer or sent to the email address, specified for your profile: click export button and select the required option.

Note

Exported file will match your current sorting, applied filters, and visibility setting.

Clients¶

The Clients section contains information about all registered traders in the B2Core UI. Here you can manage your clients.

See also

Managing clients

General¶

See also

How to create a client

This subsection contains a list of all clients registered in the in the B2Core UI.

ID: Identifier of the client in the system.
Name: Client’s name.
Created: Date and time of client’s profile creation.
Status: Current status of the client in the B2Core UI, refer to Client statuses for details.
Email: Email address the client uses to log in to the B2Core UI.
Tags: Tag(s) assigned to the client. The tags are used to adjust the display of the client list for the Back Office administrators, refer to Users for details.
Manager: Manager of the client, refer to Managers for details.
Phone: Client’s phone number.
Country: Country if specified by the client at registration/KYC, refer to Countries for countries list.
City: Client city.
Types: Client type, refer to Types for details.
Internal client type: This field is used for internal purposes only.
Verification level: Some operations in the B2Core UI may require verification of certain level, refer to Verification for details.
Company Short: Short name of the client’s company.
Company Full: Full name of the client company.
Risk level: Client trading status may vary depending on the risk level.
Last login: Date and time of client last log in to the B2Core UI.

To see details, click the edit button. Detailed info interface is split into several tabs, menu button in the upper right corner opens a drop-down list of additional tabs. These tabs will be covered in more detail in the following sections.

Client tab

The Client tab is visible by default. It contains client’s personal data and profile info such as status, verification, etc. On this tab you can also add client phone number, and dial that number via the configured provider.

Note

Disabled (gray) fields cannot be edited (most of them are system fields and filled automatically).

Note that changing the following fields values may affect client’s permissions:

Email — this field is disabled by default, but you can enable it by clicking the pencil icon. Note that this is an email address, which client uses to log in the system. History of email addresses changes you can see in Historical info tab.
Status — refer to Client statuses for details.
Client type — some restrictions may be specified depending on client’s type, refer to Types for details.
Manager — availability of some operations may vary for clients of different offices/managers, refer to Managers for details.
Verification level and Verification — some operations in the B2Core UI may require verification of certain level.
Tag — does not affect client’s permissions, but can be used by administrator to search and display clients with specified tags, refer to Users for details.
Risk level — trading status may vary depending on risk level.

Note

Birthday field is disabled by default — click the pencil icon to enable editing. Note, that a user must be at least 18 years old.

Services tab

On this tab you can view a list of paid services to which the client is connected and connect the client to a new service (Add client service).

Note

For some services it may be required to specify additional parameters when connecting a client — refer to Parameters for details.

Service full name: Service name, refer to List for details
Service group: Name of the group in which this service is included, refer to Groups for details
Status: Status of subscription

Advanced tab

On this tab you can see additional data that the client specified during registration.

The set of fields depends on the registration wizard settings.

Event Log tab

On this tab you can add notes and comments about the client. We support text formatting, hyperlinks, attachments, admin tagging, replies, and message editing.

You can tag a particular admin in the Event log you create, and the admin you have tagged will automatically get a notification email with details of the log event.

Address tab

On this tab you can view a list of client addresses and details.

Accounts tab

On this tab you can view a list of client’s accounts.

refer to Accounts for fields and explanations.

Transactions tab

Select the transaction type to view:

Deposit

A list of client’s deposits. refer to Deposits for fields and explanations.

Payout

A list of client’s payouts. refer to Payouts for fields and explanations.

Transfer

A list of client’s transfers. refer to Transfers for fields and explanations.

Exchange

A list of client’s exchanges. refer to Exchange for fields and explanations.

Balance change operation

History of balance changes made by the administrator via the Back Office, contains the following information:

Date and time of balance changing
Account number
Amount of operation
Credit/Debit type of operation
Admin user who performed the operation

Note

Balance changes by the Back Office administrator are not displayed in the Deposits and Payouts lists.

Password change history tab

See also

How to change a client password

This tab contains information about client’s password changes.

Date

Date and time of password change.

Type

Type of password changing:

Restored — client reset the password
Changed by admin — client’s password was changed by administrator

Changed by

Email address of the performer.

Settings tab

This tab is used to specify trading and account restrictions for the client.

Communication Language: refer to Localizations for a list of supported languages.
Request color: You can define the color which will be used to highlight requests of this client in Requests, and so additionally mark it for your convenience. Enter the color name or hex, or rgba, or click the grey field to pick the color from palette.
Exchange blocked: If Yes, exchange widgets in the B2Core UI are unavailable for this client. This option will overwrite the restrictions based on the verification level, refer to Verification for details.
Deposits blocked: If Yes, deposits in the B2Core UI are unavailable for this client. This option will overwrite the restrictions based on the verification level, refer to Verification for details.
Withdrawals blocked: If Yes, withdrawals in the B2Core UI are unavailable for this client. This option will overwrite the restrictions based on the verification level, refer to Verification for details.
Converter blocked: If Yes, exchanges in the B2Core UI are unavailable for this client. This option will overwrite the restrictions based on the verification level, refer to Verification for details.
Internal transfer blocked: If Yes, internal transfers between wallets in the B2Core UI are unavailable for this client. This option will overwrite the restrictions based on the verification level, refer to Verification for details.

Rights tab

On this tab you can overwrite access rights for the client. Access rights define which transactions the client can make in the B2Core UI. For details, refer to Client rights.

If you change access rights for the client individually, on this tab the new value will be displayed with *.

Options tab

Use this tab to define individual accounts limitations for this client:

Max number of demo trading accounts
Max number of live trading accounts

This values (if set) will overwrite default system limitations, refer to Products for details.

Test results tab

On this tab you can view a list of tests which the client has passed in the B2Core UI and their results. refer to Client tests for more details.

Trades tab

On this tab you can view a history of client trades.

Order ID: Order identifier on the exchange.
Instrument: Currency pair.
Side: Trade side: buy or sell.
Quantity: Trade amount in the quoted currency.
Price: Execution price.
Value: Trade amount in the base currency.
Fee: Trade commission.
Fee Product: Trade commission currency.
Date: Date and time of the trade.

MT accounts tab

On these tabs you can view a list of client’s MetaTrader accounts. The list can be divided into several tabs according to the number of active platforms.

refer to MT accounts for fields and explanations.

B2Margin accounts tab

Use this tab to monitor client’s margin accounts in B2Margin system.

ID: System record identifier.
Account ID: Identifier of B2Margin account.
Currency: Account currency.
Balance: Account total balance.
Equity: Account equity.
Margin: Account total margin.
Free Margin: Account available margin.
Unrealized PL: Current profit/loss on open positions.
Open Positions: Number of open positions.
Open Orders: Number of open orders.
Created At: Date and time of account creation.

To see details, click the account. Account details contain the following tabs:

Positions — a list of open positions
Open Orders — a list of open margin orders
Trades — a list of executed trades
Order History — a list of all margin orders opened from this account

Files tab

See also

How to upload a file

On this tab you can view, add, upload, download and delete files related to a client.

By default, folder tree on this tab corresponds to the Client folders. You can additionally create and manage custom folders as a more advanced file storage. You can create a folder tree with any nesting depth. You cannot delete the pre-defined folders on this tab. You can view only those pre-defined system folders, to which you were granted access.

If a system folder is created with the same name as that of a custom folder of some client, a _Custom postfix will be added to the name of the custom folder, and a system folder with the same name will be created next to it.

Use following buttons to get the required functionality:

Download all: Get an email with a zip file, containing all files of a particular client.
Add file: Upload client files from your computer or a cloud into the system.
Add multiple files: Use this button to upload multiple files at once.
Add directory: Create new directories.
Edit: Edit file names or move files into another directories. Files can only be moved between the directories of the same client.
Delete: Delete selected files or directories.
Cancel: Discard unsaved changes.
Save: Save new changes.

Compliances tab

On this tab you can view, add, and edit text notes or commentaries related to the client. This comment will be displayed only in the Back Office. Your client will not get any notification on it.

Comment: Internal text note on the client.
Date: Date and time when the comment was added.
Creator: Administrator who added the comment.
Last Editor: Administrator who last edited the comment.

Deposit wallets tab

On this tab you can view a list of cryptocurrency wallets that were generated for the client.

Method: Method which is used to deposit funds, refer to Deposit methods for details.
Currency: Wallet currency.
Address: Public wallet address.
Destination tag: Applicable for XRP, XLM, BNB, XEM.

Withdrawal wallets tab

On this tab you can view a list of wallets that were used by the client for withdrawal.

Method: Method which is used to withdraw funds, refer to Payout methods for details.
Currency: Wallet currency.
Address: Public wallet address.
Destination tag: Applicable for XRP, XLM, BNB, XEM.

Saved withdrawals tab

On this tab you can view a list of saved withdrawal details, which are withdrawal “patterns” which the client has saved in the B2Core UI when creating a withdrawal to avoid specifying the same information once again for each subsequent withdrawal.

Name: Provider name.
Saved at: Date and time of withdrawal saving.

By clicking the eye button, you’ll switch to the selected saved withdrawal details. The data is stored in the JSON format.

Documents tab

See also

How to use the KYC constructor

On this tab you can view a list of client’s documents used for Verification.

ID: Document identifier in the Back Office.
Type: Document type, refer to Document types for a list of supported types.

Status — current status of the client request for document approval.

Request ID: Identifier of the client request for the document approval.

2FA history tab

See also

How to disable 2FA for a client

On this tab you can get information on two-factor authentication status.

Above the table you can view current state of 2FA:

SMS — the client receives 2FA verification codes via SMS: enabled or disabled.
Google — the client receives 2FA verification codes via the Google Authenticator app: enabled or disabled.

The table contains the history of enabling/disabling client two-factor authentication:

Date: Date and time of 2FA enabling/disabling.
Enabled: Action type: 2FA was enabled or disabled.
Provider: 2FA provider.

Authorization history tab

On this tab you can view the history of the client logins to the B2Core UI.

Auth date: Date and time of login to the B2Core UI.
Auth IP: IP address from which the client logged in to the B2Core UI.
Auth location: Location (country, city) from which the client logged in to the B2Core UI, based on the IP address.
Status: Status of login: success or failed.

Historical info tab

This tab contains the history of the client’s email address changing: origin email, new email, when and by whom it was changed.

Note

For the first registered email address columns Origin email and Changed by are empty.

Devices tab

On this tab you can view a list of devices from which the client has ever logged in to B2Core UI. This list contains information on logins such as IP, OS, and browser, and Fingerprint Data which is the detailed information about the device from which the user has logged in to.

KYC data tab

See also

How to use the KYC constructor

On this tab you can view the history of client verification levels changing: new level, previous level, when and by whom it was changed, and the reason of changing.

refer to Verification for more details on access rights, based on the verification levels.

Services¶

In this subsection, you can create and manage paid services. Each client can be connected to one or more paid services individually.

Clients¶

On this page you can view a list of all clients with active and inactive paid services.

Note

To see paid services of a particular client, refer to the Services tab of the client details.

ID: Identifier of the client in the B2Core UI.
Email: Client’s email address.
Active services: A list of services to which the client is currently connected.
Inactive services: A list of disconnected services.
Client internal type: This field is used for internal purposes only.
Client type: Client type, refer to Types for details.
Company short: Short name of the client’s company.
Company long: Full name of the client’s company.
Tags: Tag(s) assigned to the client. The tags are used to adjust the display of the client request list for the Back Office administrators, refer to Users for details.
Manager: Manager of the client, refer to Managers for details.

The table additionally contains service parameters and their values specified for a corresponding client.

List¶

On this page you can view a list of all paid services created in the system:

ID: Service identifier
External system id: External system identifier.
Name: Service short name.
Full name: Service full name.
Group: Name of the group in which this service is included. refer to Groups.
Status: Current service status.
Comment: Internal text note.

Parameters¶

On this page you can configure additional parameters for each service. When adding a service to a client, these parameters values will be required.

ID: Parameter identifier.
Name: Parameter name.
Caption: Parameter description.
Services: List of services to which this parameter is applied.

To see details, click the edit button. In the details, you can select parameter type:

Text
Numeric
Date
Select
Multiselect
Checkbox
Table

Groups¶

On this page you can view a list of service groups:

ID: Service group identifier.
Caption: Service group description.
Comment: Internal text note.

Saved presets¶

On this page you can view a list of pre-configured service presets.

When adding a client service, you can select a preset from the list in the Preset option field. You can also save a configured service as a preset by clicking the Save preset button.

When deleting a service parameter, all related presets are deleted automatically.

ID: Internal identifier of the preset.
Service: Service name.
Date added: Date and time of preset creation.
Name: Name of the preset.

Requests¶

See also

Resolutions

How to create a request resolution type

How to create a request resolution

When your client creates a new request, it will appear in the requests list. All new requests are pending* and require your resolution (approve or reject), for a list of resolutions refer to Resolutions.

Requests in the list are filtered by Pending status by default for your convenience. You can also see a number of pending requests on the bell icon in the top panel.

№

Sequence number of the request.

Client ID

Identifier of the client who submitted the request.

Client name

Name of the client who submitted the request.

Client email

Email address of the client who submitted the request.

Tags

Tag(s) assigned to the client. The tags are used to adjust the display of the client request list for the Back Office administrators, refer to Users for details.

Type

Request type:

Archive — trade account archiving
Deposit — funds depositing
Payout — funds withdrawal
Transfer — internal funds transaction
External transfer — external funds transaction
Verification — changing of verification level
Profile — first name / last name changing
Account — account creation (if request is required for this product)
Introducing brokers — joining the IB program

Internal client type

This field is used for internal purposes only.

Status

Current status of the request:

Pending — request was sent but has not yet been processed by the administrator
Approved — request was approved by the administrator
Rejected — request was rejected by the administrator

Verification Level

Verification level of the client.

Date

Date of request submitting.

Processing date

Date of request resolution.

Account number

Identifier of the client’s account.

Amount

Transaction amount.

Currency

Transaction currency.

Method

Method which is used to deposit or withdraw funds, refer to Deposit methods, Payout methods for details.

Transaction ID

Transaction identifier in the system.

Company Short

Short name of the client’s company.

Company Full

Full name of the client’s company.

Dealing approved

This status is used for internal purposes only. It reflects the result of the operation check by the finance department.

Compliance approved

This status is used for internal purposes only and identifies whether a compliance check for a withdrawal operation has been passed.

Liquidity account

Client’s liquidity account, applicable only for B2Core and B2Trader solution.

To see details, click the edit button. You can add comment to the request (Add comment button) or set the color of the request in the list (Options button).

Admins with Update requests permission can also check the transaction (Audit button): the system will summarize all incoming transactions on the account and show a notification if there is a significant discrepancy in the balance.

For some providers it is also possible to edit the deposit or payout amount directly in the request.

Accounts¶

In this subsection you can view a list of all accounts of all clients.

Note

To see accounts of the specified client, refer to Accounts tab of the client details.

Account ID

Identifier of the account in the system.

Account number

Account number.

Client ID

Identifier of the account owner.

Client name

Name of the account owner.

Client status

Current status of the account owner in the B2Core UI, refer to Client statuses for details.

Email

Email address of the account owner.

Tags

Tag(s) assigned to the account owner. The tags are used to adjust the display of the accounts for the Back Office administrators, refer to Users for details.

Phone number

Phone number of the account owner.

Country

Account owner country, refer to Countries for a list of countries.

Company

Account owner company.

Product

Refer to Products for details.

Platform

Refer to Platforms for details.

Type

Account type:

Personal
Trade
Demo
Partner
Liquidity

Currency

Account currency.

Leverage

Account leverage.

Balance

Account total balance in account currency.

Balance (USD)

Account total balance in USD.

Balance (EUR)

Account total balance in Euro.

Hold amount

Account locked balance.

Free funds

Account available balance.

Equity

Account equity for MetaTtader accounts.

Free margin

Account available margin for MetaTtader accounts.

Internal client type

This field is used for internal purposes only.

Client verification level

Verification level of the account owner.

To see account details, select the required account and click the edit button. The detailed info contains the following tabs:

Account — details of the account, access rights and owner.
Transactions — select the transaction type to view a list of operations. Fields and details are described in the corresponding sections of this guide.

Note

To see information on transactions of the specified client, refer to Transactions tab of the client details.

Managers¶

In this subsection you can view a list of all managers to which the clients can be assigned.

Name: Manager’s name.
Email: Manager’s email address.
Title: For example, Mr. or Mrs..
Enabled: Manager status.

To see details, click the edit button. Detailed info additionally contains Phone field.

Types¶

In this subsection you can view and manage clients types.

ID: Type identifier.
Name: Type name.
Caption: Type description.
Enabled: If Yes, this client type is available for selection.
Default: If Yes, this type is default for new clients.
Num. of clients: Total number of clients of this type.

Introducing brokers¶

Introducing brokers is a partnership program which allows your clients to become your partners and referring traders to start earning revenue when referred clients begin trading in real market. In the program, you pay your partners only a percentage of the profit already received for trades.

To learn more, refer to product documentation.

MT accounts¶

The MT Account section provides information on clients MetaTrader 4 and MetaTrader 5 accounts.

MT4 accounts¶

In this subsection you can view a list of all MetaTrader 4 accounts of all clients.

Note

To see MT4 accounts of a particular client, refer to the MT accounts tab of the client details.

The list contains customer identifiers in the system and all basic information about MetaTrader accounts. The list can be divided into several tabs according to the number of active platforms.

To switch to the account details, click the edit button. Detailed info contains the following tabs:

Open positions — a list of open positions and details, this tab is displayed by default.
All deals — a list of all closed positions.
Pending orders — a list of all Limit orders.
Deposits/Withdrawals — a list of all deposits and withdrawals on the account.

MT5 accounts¶

In this subsection you can view a list of all MetaTrader 5 accounts of all clients. The structure of this subsection repeats the structure of the MT4 accounts subsection.

Note

To see MT4 accounts of a particular client, refer to the MT accounts tab of the client details.

Finance¶

The Finance section provides information on clients transactions history.

See also

Managing finances

Deposits¶

See also

How to create a deposit

This subsection contains a list of all deposits on clients accounts and general information.

Note

To see deposits of a particular client, refer to the Transactions tab of the client details.

Deposit number: Sequence number of the deposit in the system.
Client ID: Client identifier in the system.
Client: Client name.
Email: Client email address.
Tags: Tag(s) assigned to the client. The tags are used to adjust the display of the deposits list for the Back Office administrators, refer to Users for details.
Country: Client country, refer to Countries for a list of countries.
Company Short: Short name of the client company.
Company Full: Full name of the client company.
Account number: Account number to which the deposit is credited.
Payment method: Method which is used to deposit funds, refer to Deposit methods for details.
Payment name: Method name in the system.
Groups of method: refer to Deposit groups.
Amount: Deposit amount.
Currency: Deposit currency.
Vendor Commission: Brokerage commission amount.
Provider Commission: Payment system commission.
Commission currency: Currency in which the commission was charged.
Final amount: In the currency of crediting minus commissions.
Final currency: Currency of crediting.
Rate: Exchange rate.
Rate currency: Currency of the rate.
Rate (USD): Exchange rate in USD.
Final amount (USD): In USD after commissions.
Created: Date and time of deposit creation.
Status: Current deposit status, refer to Transaction statuses for details.
Fin verified: This status is used for internal purposes only. It reflects the result of the operation check by the finance department.
Account type: Product type, refer to Products for details.
Internal client type: This field is used for internal purposes only.
Invoice: Unique identifier of the payment in the payment system.
Transaction: Link to the transaction.

To see payment info, click the edit button or Deposit number. Payment info contains:

ID: Sequence number of the deposit in the system.
Status: Current deposit status, refer to Transaction statuses for details. The status of the transaction can be changed in the Edit mode.
Invoice: Unique identifier of the payment in the payment system.
Deposit method: Method which is used to deposit funds, refer to Deposit methods for details.
Date: Date of deposit creation.
Invoice date: Date of invoice creation.
Result date: Date of deposit crediting.
Fin verified: This status is used for internal purposes only. It reflects the result of the operation check by the finance department. The status of this field can be changed only by admin users with the appropriate access rights.
Amount: Deposit amount.
Currency: Deposit currency.
Vendor Commission: Brokerage commission amount.
Provider Commission: Payment system commission.
Final amount: In the currency of crediting minus commissions.
Transaction: Transaction hash. This filed can be changed in the Edit mode.
Rate (USD): Exchange rate in USD. The Rate can be changed in the Edit mode. The new rate will be saved and the Final amount of the transaction will be recalculated.
Internal comment: Type here any comments on operation (if needed), then click Save.
Account number: Account number.
Account balance: Current account balance.
Account type: Product type, refer to Products for details.
Client: Client’s name.
Email: Client’s email address.

You can check this transaction using the button in the Transaction monitoring section of the payment info. The button has the following states:

Check transaction — transaction has not yet been checked. You can send a check request.

Request sent — the check request has already been sent. Repeated request is not available. You can check the result in the Transaction monitoring section.

Request in process — the check request has already been sent but takes longer time than expected. Repeated request is not available.

The button unavailable — this transaction has already been checked. Repeated request is not available. You can check the result in the Transaction monitoring section. Repeated request is not available.

Payouts¶

See also

How to create a payout

This subsection contains a list of withdrawals from clients accounts and general information. Click the ID to view payout’s details.

Note

To see payouts of a particular client, refer to the Transactions tab of the client details.

Withdrawal number: Sequence number of the payout in the system.
Client ID: Identifier of the client in the B2Core UI.
Client: Client’s name.
Email: Client’s email address.
Tags: Tag(s) assigned to the client. The tags are used to adjust the display of the payouts list for the Back Office administrators, refer to Users for details.
Country: Client country, refer to Countries for a list of countries.
Company Short: Short name of the client company.
Company Full: Full name of the client company.
Account: Account number from which funds are withdrawn, refer to Deposit methods for details.
Method: Method which is used to deposit funds, refer to Payout methods for details.
Name: Method name in the system.
Groups of method: Refer to Deposit groups.
Amount: Payout amount.
Currency: Payout currency.
Vendor Commission: Brokerage commission amount.
Provider Commission: Payment system commission.
Commission currency: Currency in which the commission was charged.
Final amount: In the currency of debiting after commissions.
Final currency: Currency of debiting.
Rate: Exchange rate
Rate currency: Currency of the rate.
Rate (USD): Exchange rate in USD.
Final amount (USD): In USD after commissions.
Status: Current payout status, refer to Transaction statuses for details.
Created: Date and time of payout creation.
Processed: Date and time of payout processing.
Account type: Product type, refer to Products for details.
Internal client type: This field is used for internal purposes only.
Invoice: Unique identifier of the payment in the payment system.
Transaction: Link to the transaction.
Blockchain fee: Blockchain commission for the transaction.
Wallet: Public wallet address.
Destination Tag: Applicable for XRP, XLM, BNB, XEM.
Dealing approved: This status is used for internal purposes only. It reflects the result of the operation check by the finance department.
Compliance approved: This status is used for internal purposes only and identifies whether a compliance check for a withdrawal operation has been passed.

To see payout info, click the withdrawal number. Payout info contains:

ID: Sequence number of the payout in the system.
Status: Current payout status, refer to Transaction statuses for details.
Invoice: Unique identifier of the payment in the payment system.
Date: Date of payout creation.
Invoice date: Date of invoice creation.
Result date: Date and time of payout debiting.
Method: Method which is used to withdraw funds, refer to Payout methods for details.
Amount: Payout amount.
Currency: Payout currency.
Vendor Commission: Brokerage commission amount.
Provider Commission: Payment system commission.
Final amount: In the currency of debiting minus commissions.
Internal comment: Type here any comments on operation (if needed), then click Save.
Dealing approved: This status is used for internal purposes only. It reflects the result of the operation check by the finance department. The status of this field can be changed only by admin users with the appropriate access rights.
Compliance approved: This status is used for internal purposes only and identifies whether a compliance check for a withdrawal operation has been passed. The status of this field can be changed only by admin users with the appropriate access rights.
Request Info: Client request, related to the payout: identifier, resolution, and date of resolution.
Account: Account number.
Account balance: Current account balance.
Account type: Product type, refer to Products for details.
Client: Client name.
Email: Client email address.

You can check this transaction using the button in the Transaction monitoring section of the payment info. The button has the following states:

Check transaction — transaction has not yet been checked. You can send a check request.

Request sent — the check request has already been sent. Repeated request is not available. You can check the result in the Transaction monitoring section.

Request in process — the check request has already been sent but takes longer time than expected. Repeated request is not available.

The button unavailable — this transaction has already been checked. Repeated request is not available. You can check the result in the Transaction monitoring section. Repeated request is not available.

Deposit wallets¶

This subsection contains a list of deposit wallets with specified adresses, currencies, and deposit methods.

Note

To see wallets of a particular client, refer to the Deposit wallets tab tab of the client details.

ID: Wallet identifier in the system.
Client ID: Wallet’s owner identifier.
Client: Wallet’s owner name.
Tags: Tag(s) assigned to the client. The tags are used to adjust the display of the payouts list for the Back Office administrators, refer to Users for details.
Address: Wallet address.
Destination tag: Applicable for XRP, XLM, BNB, XEM.
Method: Method which is used to deposit funds, refer to Deposit methods for details.
Currencies: Wallet currency.

Transfers¶

See also

How to create a transfer

This subsection contains a list of funds transfers between accounts and general information.

Note

To see transfers of a particular client, refer to the Transactions tab of the client details.

Operation ID: Transfer identifier in the system.
Client ID: Client’s identifier in the B2Core UI.
Client: Client’s name.
Email: Client’s email address.
Tags: Tag(s) assigned to the client. The tags are used to adjust the display of the transfers list for the Back Office administrators, refer to Users for details.
Company Short: Short name of the client company.
Company Full: Full name of the client company.
From account: Account from which the transfer was made.
Source platform: Source account platform, refer to Platforms for details.
Source type: Source account type, refer to Products for details.
Source amount: Amount of the transfer in the currency of source account.
Source currency: Currency of the source account.
To account: Account to which the transfer was made.
Destination platform: Destination account platform, refer to Platforms for details.
Destination type: Type of the destination account, refer to Products for details.
Destination amount: Amount of the transfer in the currency of destination account.
Destination currency: Currency of the destination account.
Status: Current transfer status, refer to Transaction statuses for details.
Created: Date and time of transfer creation.
Processed: Date and time of transfer processing.

To see transfer details, click the edit button. Detailed info contains additionally internal client type, source and destination commissions paid for the transfer, and Request Info if the transfer was made via the request.

Exchange¶

See also

How to exchange funds

This subsection contains a list of currencies exchanges and general information.

Note

To see exchanges of a particular client, refer to the Transactions tab of the client details.

Transaction ID: Exchange identifier in the system.
Client ID: Client’s identifier in the system.
Client: Client’s name.
Email: Client’s email address.
Tags: Tag(s) assigned to the client. The tags are used to adjust the display of the exchanges list for the Back Office administrators, refer to Users for details.
Company Short: Short name of the client company.
Company Full: Full name of the client company.
From account: Account from which the transaction was made.
Source amount: Amount of the transaction in the currency of source account.
Source currency: Currency of the source account.
To account: Account to which the transaction was made.
Destination amount: Amount of the transaction in the currency of destination account.
Destination currency: Currency of the destination account.
Commission: Amount of commission charged.
Rate: Exchange rate
Status: Current exchange status, refer to Transaction statuses for details.
Created: Date and time of transfer creation.

Transactions¶

This subsection contains a general list of all types of transactions: deposits, payouts, transfers, exchanges.

ID: Operation identifier in the system.
Client ID: Client’s identifier in the system.
Type: Transaction type.
Source: Source currency.
Amount: Amount in source currency.
Commission: Amount of commission charged in source currency.
Destination: Destination currency.
Amount: Amount in destination currency.
Commission: Amount of commission charged in destination currency.
Status: Current transaction status, refer to Transaction statuses for details.
Date: Date of transaction creation.

Reports¶

See also

How to create a report

This subsection contains a list of created reports and general information.

ID

Report identifier in the system.

Interval

Report schedule:

Daily — the report is sent every day
Weekly — the report is sent once a week
Monthly — the report is sent once a month

Date slice

Data period (specified time is server time):

Day — previous day from 00:00 to 23:59
Week — previous week from Monday 00:00 to Sunday 23:59
Month — previous month from the first day of the month 00:00 to the last day 23:59
Curweek — previous 7 days from the first day 00:00 to yesterday 23:59
Overall — from the very beginning to yesterday 23:59
Curmonth — from the first day of the current month 00:00 to yesterday 23:59

File format

File format in which the report is sent.

Name

Report caption.

Mail to

Destination email address.

Last run

Date and time of the latest report generation.

Active

Current report status.

Bonuses¶

The Bonuses section provides brokers with the opportunity to motivate their clients to trade by introducing an automated and semi-automatic bonus reward system. A prerequisite for crediting a bonus to a client’s account is trading of a certain volume (Lot per unit), which is indicated for each specific bonus. Bonuses can be temporary or permanent, they can be set for all clients or individually, which makes the reward system customizable and flexible.

See also

Managing bonuses

Bonus presets¶

See also

How to create a bonus preset

In the Bonus Preset subsection you can view a list of bonus templates and create a new one.

ID: Identifier of the preset.
Platform: Platform of the bonus.
Name: Name of the preset.
Default: If Yes, the bonus is default for all clients.
Lifetime: The number of days after which the activated bonus expires, in days.
Lot per unit: Required amount of traded volume for bonus crediting. Must be greater than 0.
Set credit immediately: If Enabled, the bonus is credited immediately.
Ignored open/close interval: Minimal time interval during which a position must be opened for the bonus to be credited.
Ignored symbol groups: Currency pairs for which this bonus is not credited. Multiple select available.
Autoenable trading if balance > 0: If Enabled, trading with bonus funds is available only with a positive account balance. The system checks balances once an hour and deactivates bonuses for zero or negative balances.

Bonus distribution¶

In the Bonus Distribution subsection you can view a list of all bonuses credited to clients with an indication of the client’s identifier, crediting account, bonus amount, bonus state, and date of crediting.

ID

Bonus identifier in the system.

Client ID

Identifier of the client who receives the bonus.

Client name

Name of the client who receives the bonus.

Client email

Email address of the client who receives the bonus.

Tags

Tag(s) assigned to the client. The tags are used to adjust the display of the bonuses list for the Back Office administrators, refer to Users for details.

Account

Account number to which the bonus is credited.

Amount

Bonus amount.

State

Current bonus status:

Queued — new bonus
Active — bonus was credited to the account
Pending — bonus is active, traded lots are calculated
Processing — bonus is being credited/withdrawn
Completed — bonus conditions (lot per unit) were met, bonus was credited to the account balance
Expired — bonus conditions (lot per unit) were not met before the expiration date, bonus expired
Error — error occurred while crediting/withdrawing bonus

Created at

Date and time of bonus creation.

To see detailed crediting information, click the view button.

Created at

Date and time of bonus creation.

Amount

Bonus amount.

State

Current bonus status:

Queued — new bonus
Active — bonus was credited to the account
Pending — bonus is active, traded lots are calculated
Processing — bonus is being credited/withdrawn
Completed — bonus conditions (lot per unit) were met, bonus was credited to the account balance
Expired — bonus conditions (lot per unit) were not met before the expiration date, bonus expired
Error — error occurred while crediting/withdrawing bonus

Volume closed

Traded volume by the moment of the bonus expiration.

Temporary Bonus

Applicable for temporary bonuses only: bonus title, refer to Temporary bonuses for details.

Activated at

Date and time of bonus crediting.

Client

Email address of the client who receives the bonus.

Account

Account number to which the bonus is credited.

Fictive Volume

This field is used for reactivation of the expired bonus.

Lifetime (days)

The number of days after which the bonus expires.

Lot per unit

The required amount of traded volume for bonus crediting.

Set credit immediately

If Enabled, the bonus is credited immediately.

Ignored open/close interval (sec)

Minimal time interval during which a position must be opened for the bonus to be credited.

Autoenable trading if balance > 0

If Enabled, trading with bonus funds is available only with a positive account balance. The system checks balances once an hour and deactivates bonuses for zero or negative balances.

Ignored symbol groups

Currency pairs for which this bonus is not credited. Multiple select available.

Temporary bonuses¶

Temporary Bonuses are the time-limited promotions available in the B2Core UI.

In this subsection you can view a list of current temporary bonuses and create a new one.

ID: Bonus identifier in the system.
Name: Displayed title of the bonus.
Amount: Bonus amount.
Currency: Bonus currency.
Lot per unit: The required amount of traded volume for bonus crediting.
Created at: Date and time of bonus creation.
Expired: Date and time of bonus expiration.

To see details, click the edit button. Detailed info contains:

Platform: Bonus platform, refer to Platforms for details.
Name: Displayed title of the bonus.
Amount: Bonus amount.
Currency: Bonus currency.
Expired: Date and time of bonus expiration.
Lifetime (days): The number of days after which the bonus expires.
Lot per unit: The required amount of traded volume for bonus crediting.
Set credit immediately: If Enabled, the bonus is credited immediately.
Ignored open/close interval (sec): Minimal time interval during which a position must be opened for the bonus to be credited.
Autoenable trading if balance > 0: If Enabled, trading with bonus funds is available only with a positive account balance. The system checks balances once an hour and deactivates bonuses for zero or negative balances.
Ignored symbol groups: Currency pairs for which this bonus is not credited. Multiple select available.

Currencies¶

The Currencies section provides you with an opportunity to set up currencies, rates, and currency pairs.

Currencies¶

In the Currencies subsection you can view a list of all currencies and general information:

Code: System generated currency identifier.
Caption: Displayed name of currency.
Alpha: Currency alpha-code, set by administrators when the currency is created.
Status: If Enabled, this currency can be used for financial operations.

To see details, click the edit button. Detailed info contains additionally:

Markup: Sell: Sell commission, in percent.
Markup: Buy: Buy commission, in percent.
Precision: Displayed number of digits after the decimal separator.
Block explorer: If set, enables See details block for transactions in the B2Core UI.

Note

You can set the same sell/buy markup for all currencies by clicking the Change options button in the upper right corner of the currencies list and setting the values.

Rates¶

In the Rates subsection you can view a list of all rates specified to providers and currencies. The rates are displayed in the B2Core UI.

Provider: Platform name.
Enabled: If Yes, this rate is active.
From currencies: A list of base currencies, multiple select available.
To currencies: A list of quote currencies, multiple select available.

To see details, click the edit button. Detailed info contains additionally the Name field. For providers which require authorization you can specify parameters set up connection in the Options block. Click the Test connection button to try to set up connection.

Currency pairs¶

In the Currency pairs subsection, you can view a list of available currency pairs and add new pairs.

From currency: Indicates the base currency.
To currency: Indicates the quote currency.
Enabled for client: If set to Yes, this currency pair is available for exchange operations via the B2Core UI.
Rates Custom Priority: Indicates the order in which exchange rates are obtained from exchange rate providers for this currency pair.
Updated: Displays the date of the latest update to the currency pair settings.
Max amount: Indicates the maximum amount per exchange operation.
Step: Indicates the minimum step by which the amount can be changed at a time.
Hedging Enabled: If set to Yes, exchange operations for this currency pair are hedged.
Enabled for admin: If set to Yes, this currency pair is available for exchange operations via the B2Core Back Office.

Products¶

In the Products section you can find all the essential information about:

Products — wallets, accounts, etc.
Groups of products, which can help to manage the products
Platforms to which the products are implemented

See also

Managing products

Products¶

See also

How to create a wallet

In the Products subsection you can view a list of all products and general information:

ID

Product identifier, automatically generated by the system.

Name

Product title.

Caption

Product displayed name.

Platform

Platform on which the product is implemented, refer to Platforms.

Group

Group the product is included in, refer to Groups.

Type

Product type:

Personal
Trade
Demo
Partner
Liquidity
Exchange
External
System

Currency

Product currency.

Factory

Set 100 for cent accounts.

Status

Product status:

Disabled — product is inactive and not displayed in the B2Core UI. Accounts cannot be created. By default, the product is created with this status
Present — product is not displayed in the B2Core UI. Accounts can be created via the Back Office
Hidden — product is not displayed in the B2Core UI. Accounts can be created via the Back Office
Enabled — product is active
Default — product is displayed in the B2Core UI, accounts can be created

To see details, click the edit button. Detailed info contains:

Info tab

General product settings:

Leverage: Product leverage.
Group rights: Ability to share the preset access rights of the group for the product.
Rights: Product access rights.
Default account rights: Access rights for product account.
Max accounts: Maximal number of accounts that can be created.
Mail: Email notification settings.
Mail template: Template of email notification to be sent.
Start amount: Start account balance, applicable for demo accounts.
Priority: Sequence number of the product in the list.
Request Required: If Yes, opening a new account in the B2Core UI requires an administrator resolution in the Back Office.
Min deposit amount: In USD.
Autocreation on login: Product account is automatically created when client logs into the B2Core UI for the first time.
Platform block group: Deprecated.
Agent Account: IB identifier which is displayed in the account details in the B2Core UI, applicable only for products with type Trade.
First Transfer Activation: If Enabled, all accounts are created with the Trade Enabled right turned off. This right is added upon the first successful transfer to the account. Applicable for MT5 products only.

Currencies tab

Contains a list of product currencies for multi-currency accounts.

By clicking Actions you can set the following restrictions for the product account:

Country restrictions

Enable or disable the restricted access to the product account by country: select Type (Deny only or Allow only) and Rules (name of the country from the drop-down list) and click Save.

Client type restriction

Enable or disable the restricted access to the product account by client type: select Type (Deny only or Allow only) and Rules (type of a client) and click Save.

Verification Auto-Create

Enable or disable the restricted access to the product account by verification level: select Type (Deny only or Allow only) and Rules (level) and click Save.

Introducing broker restrictions

Either grant or restrict access to the product only to the clients of a particular IB partner: select Enabled (Yes or No), Type (Allow only or Deny only), Rules (specify a Client ID assigned to an IB partner; one or several Client IDs can be specified) and click Save.

With the Allow only option enabled, you grant access to the product only to the IB clients of the specified partners. IB clients of all other partners will not have access to this product.

With the Deny only option enabled, you restrict access to the product only to the IB clients of the specified partners. IB clients of all other partners will have access to this product.

Groups¶

In the Groups subsection you can view a list of product groups with specified:

ID: Group identifier, automatically generated by the system.
Priority: Group sequence number in the list.
Caption: Group displayed name.
Status: Enabled or disabled.

To see details, click the edit button. Detailed info contains additionally:

Description: Group details.
Type: Default product type, investment account or payment account.

Rights¶

In this subsection you can set up access right for groups of products. After that these access rights can be quickly added to the product by selecting the group.

ID: Identifier in the system.
Name: Group name.
Status: If Enabled, these group is available for selection in the product settings.

To see details, click the edit button. Detailed info contains Rights field: a list of access rights, multiple select available.

Platforms¶

In the Platforms subsection you can view a list of platforms with specified:

ID: Platform identifier, automatically generated by the system.
Caption: Platform displayed name.
Name: Internal system name of the platform.
Platform: Base platform.
Status: Enabled or disabled.

To see details, click the edit button. Detailed info contains additionally:

Short caption: Short name of the platform.
Demo: If Yes, clients can open demo accounts for products on this platforms.
Allow users share same accounts: If Yes, multiple clients can use the same shared account.
Use account number settings in products: If Yes, it is available to limit number of accounts for the products on this platform.
Settings: Parameters for setting up connection to the platform. Set of parameters depends on the platform.

PAMM¶

In the PAMM section you can set up connection to PAMM systems.

Links¶

In this subsection you can view a list of PAMM links. These links are displayed in the B2Core UI and are used to create PAMM accounts.

ID: Identifier of the link in the system.
Platform: Account platform, refer to Platforms for details.
Product: Only products with type Payment account, refer to Groups for details.
Caption: Link name displayed in the B2Core UI.
System settings: Location, WhiteLabel ID. Please, contact your account manager in order to retrieve the values.

To see details, click the edit button.

Promotion¶

The Promotion section provides you with an opportunity to adjust the B2Core UI dashboard, alerts and widgets visible to clients.

See also

Managing advertising options

Banners¶

See also

How to create a banner

Banners are any advertisements or news you want your clients to see in the B2Core UI. You can create unlimited number of banners and assign them to any pages of the B2Core UI (by specifying Banner URL). You can add a button to any banner that can be a link, for example, to detailed information.

ID: Banner identifier, automatically generated by the system.
Caption Light: Banner title for the light theme of the interface.
Caption Dark: Banner title for the dark theme of the interface.
Created at: Date-time of banner creation.
Created by: Email of user who created the banner.
Banner URL: Relatively to the B2Core UI URL.
Banner Priority: Banner display order.
Enabled: If Yes, the banner is displayed in the B2Core UI.

To see details, click the edit button. Detailed information contains additionally the following tabs:

Banner: On this tab you can additionally specify Button URL — if this value is specified, by clicking on the button, the client will be redirected to the specified URL.
Light: On this tab you can adjust the banner for the light theme of the interface. All fields support HTML.
Dark: On this tab you can adjust the banner for the dark theme of the interface. All fields support HTML.

Announcements¶

See also

How to create an announcement

Announcement is a notification displayed to clients via the B2Core UI.

ID

The announcement identifier, which is automatically generated by the system.

Type

The announcement type that identifies whether the announcement requires clients to take an action.

Required — the announcement contains a button and blocks further interaction with the B2Core UI until a client clicks this button.
Optional — the announcement does not require any actions from a client and is displayed as a notification.

Title

The announcement title.

Text

The announcement text.

Button URL

Specifies the URL to which a client will be redirected after clicking the button displayed in the announcement.

Button Text

Specifies the button label (this field is only available for announcements of a “Required” type).

Targeted Emails

The list of emails.

Enabled

If set to Yes, the announcement is active.

To view the announcement details, click the edit button. Detailed information contains the additional Announcement Reactions section — a list of clients who have seen the announcement (clicked a button displayed in the announcement or opened the announcement by clicking the Announcement icon) and the date and time when clients interacted with the announcement.

Dashboard¶

In this subsection you can view a list of available widgets and customize their display on the Dashboard page of the B2Core UI.

ID: Internal identifier of the widget in the system.
Caption: Widget name.
Order: Sequence number of the widget in the B2Core UI.
Sort Actions: The arrow buttons in this column are used to change the order of the widgets (sequence number in the Order column).
Delete: If the toggle is on, the widget in the B2Core UI has a close button to temporarily delete the widget (until the page is refreshed or dashboard is reset).

Menu¶

On this page you can customize the menu of the B2Core UI. Click the eye icon in the General row to see a list of available menu items. Each item has the following parameters:

ID

Internal identifier in the system.

Name

Internal name in the system.

Caption

Item name in the B2Core UI.

New

If Yes, this menu item is marked as new in the B2Core UI.

Visible

Current status of the item:

active toggle — this item is visible in the B2Core UI menu
inactive toggle — this item is hidden from the B2Core UI menu

Drag and drop the rows to change their order in the B2Core UI menu.

Click the pencil button to configure Verification level allowance. This setting determines visibility of the item to clients with a certain level of verification.

Mailing¶

In the Mailing section you can configure connections to email delivery platforms and send new emails.

See also

Managing mailing options

Marketing¶

Configuration

In this subsection you can set up connection to email sending service.

ID: Configuration identifier in the system.
Caption: Configuration description.
Platform: Email sending service name.
Status: Connection status: enabled or disabled.

To see details, click the edit button. Detailed info additionally contains the Webhook URL field and the Settings block:

Sender address: Email address registered on the email sending platform.
Sender name: This name will be displayed in letters.
API key: Key which you received when registered on the email sending platform.

Send email

See also

How to send an email

In this subsection you can view a list of outgoing emails.

ID: Email identifier in the system.
Subject: Email theme.
Description: Email text.
Created at: Date and time of email creation.
Send at: Date and time of email sending.
Platform: Email sending service name.

Click the edit button, to check sending status.

Email templates

See also

How to create an email template

In this subsection you can view a list of email templates.

ID: Email identifier in the system.
Caption: Template description.
Subject: Email theme.
Description: Email text.
Platform: Email sending service name.

System¶

Providers

In this subsection you can create and manage the SMTP server provider.

ID: SMTP server identifier in the system.
Caption: SMTP server description.
Driver: Driver used.
Host: SMTP server hostname.
Port: Port used
Username: Username as a part of credentials.
Send from: Email address of the sender.
Send from name: Name of the sender.
Encryption: Encryption type.
Enabled: Server status: true if enabled, otherwise false.
Test connection: Click the button to test existing connections.

To see details, click the edit button. Detailed info additionally contains the masked Password field.

Queue

In this subsection you can view the queue of unsent emails and delete them if necessary.

ID: Email identifier in the system.
Email: Email address.
Subject: Email subject.
Last attempt date: Date of the last attempt to send the email.
Next attempt date: Date of the next attempt to send the email.
Attempts count: Number of attempts to send the email.
Status: Email send attempt status.
Reason: Reason of unsuccessful attempt.

Log

In this subsection you can view the mailing log.

ID: Email identifier in the system.
Active queue ID: Queue identifier in the system.
Email: Email address.
Subject: Email subject.
Attempt date: Date of the last attempt to send the email.
Status: Email send attempt status.
Reason: Reason of unsuccessful attempt.

Verification¶

The Verification section provides you with an opportunity to specify verification levels, which define access rights for your clients. Verification is based on identity documents. The documents can be combined by type and included in groups for easy customization.

See also

How to use the KYC constructor

Levels¶

In the Levels subsection you can view a list of all verification levels and general information:

Index: Level index.
Caption: Level displayed name.
Description: Level description as displayed in the interface, HTML supported.
Default: If Yes, the level is default in the B2Core UI.
Visible: If Yes, the level is displayed in the B2Core UI.

To see details, click the edit button. Detailed info contains:

Index: Level index.
Wizard: System entity, it transfers a certain data scopes such as a set of documents or verification integrations, etc. to the user interface of the B2Core UI.
Caption: Level displayed name, can be localized for different interface languages.
Description: Level description, can be localized for different interface languages.
Default: If Yes, the level is default in the B2Core UI.
Visible: If Yes, the level is displayed in the B2Core UI.
Assigned Client Right: Access rights of the client with this verification level. refer to Client rights for details.
Document Groups: A set of verifying documents for this level, displayed in the Verification section of the B2Core UI. Applicable only if wizard B2B\TCA\Verification\Wizards\DocumentsWizard is used.
Limits: Transaction limits for this level, in USD.

Documents¶

In the Documents subsection you can view a list of all verification documents of all users and general information:

ID: Document identifier.
Type: Document type, refer to Document types.
Status: Current status of the client request for document approval.
Client ID: Identifier of the client who submitted the document.
Client Name: Name of the client who submitted the document.
Email: Email address of the client who submitted the document.

To see details, click the edit button. Detailed info contains:

Type: Document type, refer to Document types.
Files: Link to the document file.

Document types¶

In the Document Types subsection you can view a list of documents types and general information:

Priority: Sequence number of the document type in the list.
Name: System document type name.
Caption: Document type name, as displayed in the B2Core UI.
Status: If Enabled, this document type is used for verification.

To see details, click the edit button. Detailed info contains:

Name: System document type name.
Caption: Document type name, as displayed in the B2Core UI, can be localized for different interface languages.
Description: Document type description, as displayed in the B2Core UI, can be localized for different interface languages.
Status: If Enabled, this document type is used for verification.
Example: Example of the file.
Group: The group of documents, to which this document type is included, refer to Document groups.
Max files: Maximal number of files which can be uploaded for this type of documents.
Priority: Sequence number of the document type in the list.

Document groups¶

In the Document Groups subsection you can view a list of documents groups and general information:

Priority: Sequence number of the document group in the list.
Name: System document group name.
Caption: Document group name, as displayed in the B2Core UI.
Type: Type of the document group.
Enabled: If Yes, this group is used for verification.

To see details, click the edit button. Detailed info contains:

Name: System document group name.
Type: Type of the document group.
Caption: Document group name, as displayed in the B2Core UI, can be localized for different interface languages.
Description: Document group description, as displayed in the B2Core UI, can be localized for different interface languages.
Enabled: If Yes, this document group is used for verification.
Priority: Sequence number of the document group in the list.

Client tests¶

In this subsection, you can view a list of configured tests for client accreditation. For a test, you can specify questions that the client should answer to be granted a higher verification level in the B2Core UI.

ID: Internal identifier of the test.
Caption: Display name of the test.
Visible: If Yes, this test is available in the B2Core UI.

B2BinPay¶

In the B2BinPay section you can set up connection to B2BinPay payment system and monitor your clients wallets and withdrawals via the B2Core UI Back Office interface.

Wallets¶

In this subsection you can view a list of clients wallets:

— click to o view wallets, set up connection to B2BinPay.
— click to audit all B2BinPay deposits or withdrawals for the selected time period.

Note

Note that connection setting must be specified preliminarily (refer to External connections for details).

ID: Wallet identifier.
Currency: Wallet currency.
Confirmed balance: Available balance of the wallet, that can be used for payouts at the moment.
Pending balance: Temporarily locked balance of the wallet, that is the sum of all incoming and outgoing transfers, that have not yet received confirmation: positive number in case of deposit and negative number in case of payout. This balance cannot be used for transfers at the moment.
Unusable balance: Blocked balance, which cannot be used.
Status: Wallet status.

Withdrawals¶

In this subsection you can view a list of all withdrawals of all your clients in B2BinPay system:

Transaction ID

Withdrawal identifier.

Wallet ID

Wallet identifier.

Currency

Withdrawal currency.

Amount

Withdrawal amount.

Fee level

Blockchain fee charged for the transaction: low, medium, or high.

Created

Date and time of transaction creation.

Created by

Email of the client who created the transaction.

Processed

Date and time of transaction processing.

Processed by

Email of the administrator who processed the transaction.

Status

Current withdrawal status:

New — the withdrawal has been created and is in the queue for processing
In progress — the withdrawal has not yet received the required number of block confirmations
Done — the withdrawal is completed
Failed — the withdrawal failed in blockchain
Rejected — the withdrawal is cancelled due to security or some other reasons

Invoice

Identifier of the transaction.

Blockchain transaction

Blockchain transaction hash.

Address

Destination address.

Destination tag

Applicable for XRP, XLM, BNB, XEM.

System¶

In the System section you can adjust all the essential system parameters.

See also

Managing system settings

Key storage¶

In the Key Storage subsection you can set values for parameters which are used in Templates, like colors, images, etc.

Key storage values¶

In this page you can view and manage all the key-value pairs, stored in the system.

ID: Value identifier.
Type: Value type: string, html, mail, url.
Key: Key name which is used in Templates.
Tags: Group(s) to which this value belongs.
Value: Current value.
Status: If Enabled, this value is used.

Key storage tags¶

On this page you can view and manage tags, which are used for semantical grouping of the key values.

ID: Tag identifier in the system.
Caption: Tag description.
Status: Tag status: enabled or disabled.

Deposit systems¶

In this subsection you can set up and manage supported deposit methods.

Deposit methods¶

On this page you can view a list of all deposit methods available.

Priority: Sequence number of the method in the list.
Caption: Method description.
Name: Method name in the system.
Group: Group to which the method is included, refer to Deposit groups for details.
Provider: Provider of the deposits.
Currency: Supported currency.
Enabled: Method status.

To see details, click the edit button. Detailed info contains the following tabs:

Settings

General information and parameters to set up connection to provider. Contains the following fields:

Name: Method name in the system.
Enabled: Method status.
Group: Group to which the method is included, refer to Deposit groups for details.
Caption: Method description.
Provider: Provider of the deposits.
Result URL: URL to which the callback will be sent with notifications about the change in the status of the deposit.
Time to fund: Time of processing and crediting the deposit.
Priority: Sequence number of the method in the list.
IP White list: List of IP addresses from which it is allowed to make deposits.
Rates provider: Exchange rating provider.

TR Currencies

Currency of crediting. Contains the following fields.

ID: Currency identifier in the system.
Currency: Currency caption.
Enabled: Currency status.

PS Currencies

Payment currency. Contains the following fields:

ID: Currency identifier in the system.
Currency: Currency caption.
Enabled: Currency status in the B2Core UI.
Supported by PS: Currency status in payment system.

Commissions

In PS currencies only. Contains the following fields:

ID

Commission identifier in the system.

Currency

Commission currency.

Commission

Commission amount.

Type

Commission type:

TR — commission amount is included in the transaction amount (send less).
PSP — payment system commission, it is used only in reports for accounting of how much the payment system takes.

Deposit groups¶

Deposit groups are convenient to group deposit methods (for example, crypto deposit methods and fiat deposit methods).

Priority: Sequence number of the group in the list.
Name: Group name.
Caption: Group description.
Type: Methods type: crypto or fiat.
Enabled: Status of the group.

Payout system¶

In this subsection you can set up and manage supported payout methods.

Payout methods¶

On this page you can view a list of all payout methods available.

Priority: Sequence number of the method in the list.
Caption: Method description.
Name: Method name in the system.
Group: Group to which the method is included, refer to Payout groups for details.
Provider: Provider of the deposits.
Currency: Supported currency.
Enabled: Method status.

To see details, click the edit button. Detailed info contains the following tabs:

Settings

General information and parameters to set up connection to provider. Contains the following fields:

Name: Method name in the system.
Enabled: Method status.
Group: Group to which the method is included, refer to Payout groups for details.
Caption: Method description.
Provider: Provider of the payout.
Result URL: URL to which the callback will be sent with notifications about the change in the status of the payout.
Time to fund: Time of processing the payout.
Priority: Sequence number of the method in the list.
IP White list: List of IP addresses from which it is allowed to make payouts.
Rates provider: Exchange rating provider.
Provider Settings: Individual limits or configurations for this provider.
Custom Fields: Applicable for Constructor provider only. A configurable list of additional fields which will require values when creating a payout.

TR Currencies

Currency of payment. Contains the following fields:

ID: Currency identifier in the system.
Currency: Currency caption.
Enabled: Currency status.

PS Currencies

Currency of crediting. Contains the following fields:

ID: Currency identifier in the system.
Currency: Currency caption.
Enabled: Currency status in the B2Core UI.
Supported by PS: Currency status in payment system.

Commissions

In PS currencies only. Contains the following fields:

ID

Commission identifier in the system.

Currency

Commission currency.

Commission

Commission amount.

Type

Commission type:

TR — commission amount is included in the transaction amount (send less).
PSP — payment system commission, it is used only in reports for accounting of how much the payment system takes.

Payout groups¶

Payout groups are convenient to group payout methods (for example, crypto payout methods and fiat payout methods).

Priority: Sequence number of the group in the list.
Name: Group name.
Caption: Group description.
Type: Methods type: crypto or fiat.
Enabled: Status of the group.

Wizards¶

See also

How to change the wizard workflow

How to configure the registration wizard

The Wizards tool provides you with an opportunity to configure some parts of workflow on the side of the Back Office.

Adding and configuring the wizards is carried out at the level of the system source code. For each wizard, a list of default steps and a list of available steps are set. On the Back Office side, you can add/remove steps from the available ones, change their order and priority.

You can have more than one configured wizard for each workflow scenario. In this case, you need to select the default one which will be used by the B2Core UI. The other scenarios can be used by external systems to perform the actions via the API.

Supported wizards are listed below. Steps which will be added to the wizard by default are marked with *.

Registration

Registering a new client in the system. Each step of the wizard can have display restrictions (for example, restrictions by user type or by country). For this wizard adding the custom fields is available for steps Main form and Additional information.

Step	Description	Priority
Main form *	The system waits for basic client information	First
Client registration *	Registering a new client based on the previously entered data	Last
Client type	The system waits for information about the type of client being created	Not the first and not the last
Confirmation by email	The system sends a verification code to the client by email and waits for this code to be entered	Not the first and not the last
Confirmation by phone	The system sends a verification code to the client by the phone and waits for this code to be entered	Not the first and not the last
Captcha	Captcha creation	Not the first and not the last
Client phone number form	The system waits for information about the client’s phone number	Not the first and not the last
Additional information	The system waits for additional information about the client	Not the first and not the last

Password Recovery

Recovery of the client’s password via the B2Core UI.

Step	Description	Priority
Client identification *	Search for a client in the system by the email sent in the request	First
Confirmation by email *	The system sends a verification code to the client by email and waits for this code to be entered	Not the first and not the last
Password change *	The system waits the new entered password from the client and registers it as the current one	Last

Password change

Changing of the client’s password via the B2Core UI.

Step	Description	Priority
Confirmation by email *	The system sends a verification code to the client by email and waits for this code to be entered	Not the last
Password change *	The system waits the new entered password from the client and registers it as the current one	Last

Client type change

Changing of the current client type to corporate.

Step	Description	Priority
Blank form *	—	First
Detailed corporate information	The system waits for detailed corporate information from the client	Not the first
Additional corporate information	The system waits for additional corporate information from the client	Not the first
Bank information	The system waits for information about the bank from the client	Not the first
Bank information	The system waits for information about the bank from the client	Not the first
Representative person information	The system waits for information about the representative from the client	Not the first
Director and shareholders information	The system waits for information about the director and shareholders from the client	Not the first
Confirming the previously entered information	The system waits for the client to confirm that all information entered in the previous steps is correct and up-to-date	Not the first
Uploading corporate documents	The system waits for the client to upload files confirming the previously entered information	Not the first

Profile change

Changing of the basic information about the client.

Step	Description	Priority
Update information *	The system waits for updated client profile information	Single

Phone change

Changing of the client’s phone number.

Step	Description	Priority
Update phone number *	The system waits for client’s new phone number	First
Confirmation by phone	The system sends a verification code to the client by the phone and waits for this code to be entered	Last

Address change

Changing of the client’s address.

Step	Description	Priority
Update address *	The system waits for client’s new address	Single

Authorization

Authorization in the B2Core UI.

Step	Description	Priority
Captcha	The system checks for bots and robots	First
Login and password verification	The system waits for the client to enter username and password	Not the first
2FA	The system shows a list of available services for authorization with 2FA, waits for the client to select an authorization service, then delegates the process to this service	Not the first

2FA change

Disabling 2FA.

Step	Description	Priority
Confirmation by email *	The system sends a verification code to the client by email and waits for this code to be entered	Not the last
Confirmation by phone	The system sends a verification code to the client by the phone and waits for this code to be entered	Not the last
Disabling 2FA *	The system disables 2FA for the client	Last

Whitelist creation

Creating white lists for wallet addresses.

Step	Description	Priority
Creating white list *	The system creates a new white list for entered `wallet_address`	First
Confirmation by email *	The system sends a verification code to the client by email and waits for this code to be entered	Not the first
Confirmation by phone	The system sends a verification code to the client by the phone and waits for this code to be entered	Not the first

Whitelist delete

Deleting a previously created white list.

Step	Description	Priority
Confirmation by email *	The system sends a verification code to the client by email and waits for this code to be entered	Any
Confirmation by phone	The system sends a verification code to the client by the phone and waits for this code to be entered	Any

Whitelist change

Disabling a previously created white list.

Step	Description	Priority
Confirmation by email *	The system sends a verification code to the client by email and waits for this code to be entered	Not the last
Confirmation by phone	The system sends a verification code to the client by the phone and waits for this code to be entered	Not the last
White list disabling *	The system disables the white list	Last

Withdrawals

Processing the withdrawal operations. A Client Request will be created, the status of the created withdrawal will be set to Pending.

Step	Description	Priority
Creating new withdrawal *	The system creates a new withdrawal operation with status `New`	First
Confirmation by email *	The system sends a verification code to the client by email and waits for this code to be entered	Not the first
Confirmation by phone	The system sends a verification code to the client by the phone and waits for this code to be entered	Not the first

In the Wizards subsection of the Back Office you can a view a list of all available wizards and its statuses:

ID: Wizard identifier in the system
Name: Internal system name of the wizard
Type: Type of workflow
Enabled: If Yes, the wizard is active
Default: If Yes, the wizard is used by default for the selected type of workflow (for example, if you have several configured registration wizards at the same time)

To see wizard details, click the edit button. Detailed information contains the following tabs:

Wizard — main wizard parameters.
Workflow — steps of the wizard with priority. You can add/remove available steps and configure Country/Client Type restrictions for each step (Actions).

Bulk actions¶

Bulk actions provide you with an opportunity to perform the action, such as ban, status change, make deposit, etc., to multiple clients at once.

Name: Action name.
Action: Action type.
Status: Action result.
Created at: Date and time of action creation.
Updated at: Date and time of action update.
User: Email of user who created the action.

To see action details, click the edit button. Detailed information contains additionally:

Caption: Action description.
Log message block: Result of action.
System log block: Log of action processing.

Event Calendar¶

See also

How to manage calendar events

The Event Calendar page displays a calendar grid and allows you to manage events for admin users or other users who have access to your B2Core Back Office.

In the upper-right corner of the screen, choose a view: Month, Week, Day or List.

To move between dates, use the arrows located in the upper-left corner of the screen. To return to today’s date, click Today.

Operation types¶

In this subsection you can view all types of operation supported in the system.

ID: Operation type identifier in the system.
Caption: Operation type description.
Name: Operation type name in the system.
Class: Operation type class in the system.
Status: Enabled or disabled.

To see operation type details, click the edit button. Depending on the type, detailed information may contain additional options, such as:

Allowed operation status — a list of operation statuses which are displayed in the B2Core UI. Available for payouts, deposits, exchanges, transfers.
Holds — if Enabled, when a new payout is created its amount is blocked on the client’s account before debiting. Available for payouts.
Restrictions — general restriction for a specific type(s) of transfers. Available for transfers.
Hedging Restrictions — for selected client types exchanges will not be hedged. Available for exchanges. Multiple select available.

Countries¶

A list of countries which are available to select at registration (if a client requires to specify it). Enabled countries are displayed in the list, disabled are hidden.

Note

You cannot add a new country or edit the existing one, only to set visibility.

ID: Country system identifier.
Name: Country name (for example, Russia).
Full name: Country full name (for example, Russian Federation).
Country code: System country code
ISO 3166-2: Country geocode as per ISO 3166-2.
ISO 3166-3: Country geocode as per ISO 3166-3.
Capital: Capital of the country.
Citizenship: Demonym (for example, Russian).
Currency: National currency.
Currency symbol: Nation currency designation.
Currency code: 3-letter currency code.
Currency sub unit: Fraction of the main currency unit (for example, cent).
Region code: Region code as per UN M49.
Sub region code: Subregion code as per UN M49.
Enabled: Toggle defines if the country is available for selection during registration.

External connections¶

In this subsection you can view a list of external services and systems connected to the B2Core UI.

ID: Connection identifier in the system.
Caption: Connection caption.
Name: Connected system name.
Type: Payment system or other.
Provider: Connection provider.

To see details, click the edit button. In the details you can enable/disable connection. Detailed info contains additional Settings blocks: parameters to set up and configure connection to provider (service URL, credentials, etc.).

Filesystems¶

Filesystems are available storages for files that are uploaded to the system (for example, by the client during verification). Filesystems can be local or external.

ID: Filesystem identifier.
Name: Filesystem caption.
Provider: Filesystem provider name or local.

To see filesystem details, click the edit button. External filesystems detailed info contains additional Provider settings block to set up connection.

Localizations¶

See also

How to add/remove a language

In this subsection you can view a list of supported languages. They are available for the Back Office fields which support localization.

ID: Language identifier in the system.
Caption: Language name.
Fallback: Fallback language to be used if no translation to the main language is specified.
Priority: Sequence number of the language in the list.
Enabled: If Yes, this language is displayed in the list.

To see language details, click the edit button. Detailed info contains:

Caption: Language name.
Locale: Locale code in the system.
Language code: Language code in the system.
Fallback: Fallback language to be used if no translation to the main language is specified.
Enabled: If Yes, this language is displayed in the list.
Default: If Yes, this language is default for the B2Core UI.
Right to Left: If Yes, this language uses right to left scripts.
Priority: Sequence number of the language in the list.

Requests¶

In this subsection you can set reject reasons for Requests.

Resolutions¶

See also

How to create a request resolution

If you reject a client’s request, select a resolution — reason of rejection. On this page you can view a list of available resolutions.

ID: Resolution identifier in the system.
Caption: Resolution description.
Enabled: Resolution status.
Type: Type of the resolution, refer to Resolution types for details.

Resolution types¶

See also

How to create a request resolution type

Resolution types are used to group resolutions.

ID: Resolution type identifier in the system.
Caption: Resolution type description.
Enabled: Resolution type status.

Templates¶

In this subsection you can set up and manage mailing templates. The email is sent automatically when the specified event occurs (refer to Template types). In the templates, you can use keys which will be automatically replaced with the values specified in the system (refer to Key storage for details).

Template types¶

Template types are the codes of the events, upon which the email sending occurs.

Name: Event name in the system.
Caption: Event description.
Enabled: If Yes, automatic email sending is enabled for this type of event.

Templates¶

On this page you can view a list of existing templates.

Type: Template type, refer to Template types.
Locale: Email language.
Subject: Email subject.
Enabled: Status of the template: enabled or disabled.

To view the template itself, click the edit button. In the Template window you can view or edit an HTML-code of the email. Key storage values are supported. Click the Preview button to preview the rendered email.

SMS¶

SMS can be used, for example, to send 2FA codes or to confirm registration. In this subsection you can manage SMS templates and providers.

Providers¶

On this page you can view a list of connected SMS providers.

Name: Provider code in the system.
Caption: Provider name.
Provider: Provider (select from the list).
Enabled: Provider status.

Click the edit button to view Provider Settings used to set up connection.

SMS templates¶

On this page you can view a list of all SMS templates.

Name: Template name in the system.
Caption: Template description.
Enabled: If Yes, this template is used.

To view the template itself, click the edit button. In the Template field you can view or edit SMS text. Key storage values are supported.

Settings¶

Google Authenticator

Specify Service name to display this name in Google Authenticator app.

Bonuses

Enable or disable automatic crediting of the bonus to the client upon transfer to the trading account. The following bonus options are available:

Autocreate from deposit: If Enabled, this bonus is Active.
Autocreated bonus percent: Percentage of the transfer amount that will be credited to the client as a bonus.
Auto Bonus Limit: A maximum sum of bonuses that can be auto generated to a client. When the overall amount of auto created bonuses to a client reaches the specified limit, new auto created bonuses will not be generated.
Auto Bonus Minimum: A minimum amount of funds transfer to an MT account that will trigger an automatic bonus generation. Applies to each funds transfer to an MT account, and not to an overall sum of all deposits.
Burn on withdrawal: If Enabled and a client makes a withdrawal — all bonuses calculated for a particular account will be burnt and marked as Expired.
Burn if balance < 0: If Enabled, this bonus burns if the client’s balance becomes zero or negative.

Metatrader 4

Partner program enabled – if enabled, then clients can see their agent account’s identifier in the MT4 trading account details.
Cashback value – a fixed amount in relative units (not percentage) that will be paid to traders as a cashback for each traded lot. The cashback amount can be either integer or decimal number. The calculation formula is: cashback = lots amount × cashback value.
Cashback currency – a cashback currency in which the trading volume will be calculated and cashback will be credited. Cashback currency has to match an MT4 account currency, otherwise a trader will not be able to receive a cashback. Refer to How to set a cashback for more information.
Account destination type — trade or personal.

If the trade type is selected, the cashback will be credited to the account from which the trades were made. If the account currency does not match the currency set in Cashback currency, the cashback will be credited to another client’s account on the same platform, nominated in the corresponding currency.

If the personal type is selected, the cashback will be credited to the client’s personal-type account, nominated in the corresponding currency.

Metatrader 5

Partner program enabled – if enabled, then clients can see their agent account’s identifier in the MT5 trading account details.
Cashback value – a fixed amount in relative units (not percentage) that will be paid to traders as a cashback for each traded lot. The cashback amount can be either integer or decimal number. The calculation formula is: cashback = lots amount × cashback value.
Cashback currency – a cashback currency in which the trading volume will be calculated and cashback will be credited. Cashback currency has to match an MT5 account currency, otherwise a trader will not be able to receive a cashback. Refer to How to set a cashback for more information.
Account destination type — trade or personal.

If the trade type is selected, the cashback will be credited to the account from which the trades were made. If the account currency does not match the currency set in Cashback currency, the cashback will be credited to another client’s account on the same platform, nominated in the corresponding currency.

If the personal type is selected, the cashback will be credited to the client’s personal-type account, nominated in the corresponding currency.

Google ReCaptcha

When enabled, Google ReCaptcha is added to log in and registration. Specify your ReCaptcha key and secret to set up. refer to How to add Google ReCaptcha for step-by-step description.

Information Showing

Display or hide wallets and profiles identifiers in Wallets, History, and Profile sections of the B2Core UI.

User Confirmation Settings

Limits of attempts to confirm authorization or password changing. The following bonus options are available:

Amount of Tries: Permissible number of unsuccessful email confirmations (withdrawals, registration, password reset, 2FA disable request, password recovery). Defaults to 5. If exceeded, the system blocks new attempts for a Client Confirmation Block Time.
Client Confirmation Block Time: Period of time during which email confirmations will be unavailable after exceeding Amount of Tries limit. Defaults to 10 minutes.
Client Confirmation Failed Interval: Period of time during which new attempts of email confirmation are taken into account.
Confirmation Try Limit: Permissible number of unsuccessful confirmation via email or 2FA attempts. Defaults to 5.

User Auth Settings

Limits of attempts to authorize or change password. The following bonus options are available:

Sign in Tries Before Blocking: Permissible number of unsuccessful authorization attempts. Defaults to 5.
Client Block Time: Period of time during which new attempts to log in will be unavailable after exceeding Sign in Tries Before Blocking limit.
Client Auth Failed Interval: Period of time during which new attempts to log in are taken into account.

Client Settings

If Unique phone option is enabled, a new client cannot register in the system with a phone number that was previously used for registration. Applicable only for clients using a phone number to register.

Register settings

If Auto password generation options is enabled, the passwords for newly registered clients are automatically generated.

Weblate

Specify endpoint, project, and API key to set up integration with the Weblate platform.

Exchange

Set up lifetime interval for exchange rates in the B2Core UI.

Root folders

This section displays a list of all root folders created in General > Clients > Client details > Files. You can grant selected users the right to access root folders by specifying their email in the details tab of the root folder. To do that, click the edit button on the left of the root folder name. If a client has two root folders with identical names, the list will only display one of them, and any root settings you set to one of such folders will automatically apply to the other folder too.

Users¶

See also

How to add an admin user

In this subsection you can view and manage the administrators of the B2Core UI Back Office.

ID: Administrator identifier in the system.
Name: Administrator name.
Email: Email which the administrator uses to log in the system.
Allowed Client Tags: Clients with only these tags can be seen by the administrator in Clients, Clients Requests, Deposits, Payouts, Transfers, etc.
Status: Administrator status: enabled or disabled (cannot log in to the system).

Two Factor Authentication: Status of 2FA.
IP Whitelist: Whitelisted IP addresses of the user, refer to White lists.
Groups: A list of groups to which the user is included, refer to Groups.

Groups¶

In this subsection you can view a list of all user groups in the system and manage the access rights.

ID: Group identifier in the system.
Group: Group name.

To see details, click the edit button. Detailed info contains the following tabs:

Group — a list of permissions for users included in this group
Users — a list of users included in this group

Events¶

In this subsection, you can set filters for detecting certain events in the system (Event handler properties) and workflows for processing them (Event handler workflow).

ID: Event identifier in the system.
Short description: Event description.
Event: Event code.
Event handler workflow: The instruction to be executed upon event triggering.
Enabled: If Enabled, then the handler is active.

To view event details, click the edit button. Detailed information contains Event handler properties — filters for events and Event handler workflow — a set of fields and available setting depends on the event type, they are described in more detail in the following section.

Successful registration

When a new client is signed up to the B2Core UI or an admin user creates a new client profile via the B2Core Back Office, an email notifications is sent to the target email addresses.

The following properties of the Event handler workflow are available:

Emails: A list of emails, to which the notification about the transfer will be sent.
Template: A template for the email that will be sent upon the event, refer to Templates for details.

Transfers

Upon receiving a transfer to an account in a given platform, an email notifications is sent to the target email addresses.

The following properties of the Event handler workflow are available:

Destination Platform Id: Required parameter.
Source Platform Id: Optional parameter.
Minimum Amount: Optional parameter.
Available workflows: A list of available workflows. Depends on selected handler.
Emails: A list of emails, to which the notification about the transfer will be sent.
Template: A template for the email template that will be sent upon the event, refer to Templates for details.

Account created

When opening an account for a client, a POST request is sent to a provided external URL. Request body contains the following data:

Client ID
Client Email
Account Number
Product Name (refer to Products for details)
Product Group Type (refer to Groups for details)
Product Platform (refer to Platforms for details)

The following properties of the Event handler workflow are available:

External endpoint: External URL to which a POST request will be sent.
Content type: The following values are supported: application/x-www-form-urlencoded, application/json.

Transaction verifying

Once a RED transaction is detected in Transaction monitoring, an email notification will be sent to the target email addresses. The notification contains the following data:

Client Email
Transaction ID
Transaction Hash
Risk Score
Transaction amount

The following properties of the Event handler workflow are available:

Emails: A list of emails, to which the notification about the suspicious transaction will be sent.
Template: An email template that will be sent upon the event, refer to Templates for details.

Hedging failed

Once a hedging is failed for an exchange operation, an email notification will be sent to the target email addresses or Slack channel. The notification contains the transaction ID.

The following properties of the Event handler workflow are available:

Available workflows

Type of the notification that will be sent:

SendNotificationFlow — email notification
SendSlackNotificationFlow — Slack notification

Emails

A list of emails to which the notification about the hedging failed will be sent. Applicable for SendNotificationFlow.

Slack Webhook URL

Webhook to the Slack channel to which the notification about the suspicious transaction will be sent. Applicable for SendSlackNotificationFlow.

Template

An email/Slack template that will be sent upon the event triggered, refer to Templates for details.

Request receiving

Once a client request of a specified type is craeted, an email notification will be sent to the target email addresses. The notification contains the following data:

Request ID
Request type
Client name
Email
Date

When creating an event, you need additionally to select request Types that will trigger notification. Multiple select available.

The following properties of the Event handler workflow are available:

Emails: A list of emails to which the notification about the new request will be sent.
Template: An email template that will be sent upon the event triggered, refer to Templates for details.

Client rights¶

In this subsection, you can create and edit access rights levels for your clients. Access rights define which transactions the client can make in the B2Core UI.

To apply access rights set, set up verification levels.

Note

You can set personal access rights for a client in the profile. refer to Rights tab for details.

Caption: Description of the level.
Created At: Date and time of the level creation.
Updated At: Date and time of the level editing.
Default (Y/N): If Y, this access level is default and is assigned to a client with initial verification level.

To see details, click the edit button. The detailed information contains the following fields:

Name: Name of the level.
Caption: Description of the level.
Parent Role: Previous level. Not applicable for default level.
Converter: If selected, the client can exchange funds in the B2Core UI.
Deposits: If selected, the client can deposit funds in the B2Core UI.
Withdrawals: If selected, the client can withdraw funds in the B2Core UI.
Internal Transfers: If selected, the client can transfer funds between wallets in the B2Core UI.

Client folders¶

On this page you can view and manage a folder tree with any nesting depth, pre-defined for all clients. Folders configured on this page will be displayed on the Files tab in the client’s details. When renaming a folder on this page, it is automatically renamed on the Files tab in the client’s details.

Note

Admin users can create custom folders for a specific client on the Files tab, but the pre-defined folders cannot be edited or removed.

If a system folder is created with the same name as that of an existing custom folder of some client, a _Custom postfix is added to the name of the custom folder, and a system folder with the same name is created next to it.

Permissions:

You can assign access permissions to a folder, to specify which groups of users can view and edit it in the Files tab.
By default, nested folders inherit the access permissions from the parent folder. Their access permissions cannot be broader than that of the parent folder.
When access permissions assigned to a parent folder are revoked from a user group, access to all nested folders is automatically restricted for these users.
After access to a parent folder is granted to a user group, this group will NOT be automatically granted access to nested folders.

In the folders list you can see a list of created top-level folders:

Name: Name of the folder.
Created at: Date and time of folder creation.
Updated at: Date and time when the folder was changed.

To see folder details, click the edit button. Each folder has the following tabs:

Directory: Folder path.
Subdirectories: A list of nested folders of the parent folder. Nesting depth is unlimited, and each folder can have its own subdirectories as well. Breadcrumbs are displayed at the top of the page for convenient navigation.
Access rights: A list of available admin user groups and toggle switches, which show whether the users from this group can view the folder and its content on the Files tab in the client’s details. Note that you can use the Turn on all and Turn off all buttons to quickly provide or restrict access to folders.

Security¶

Search by IP¶

In this subsection you can view a list of logins to the system.

Client ID: Identifier of the client in the system.
Client: Client’s name.
Client email: Email address of the client.
IP: IP address from which the client logged in to the system.
Auth date: Date and time of the authorization.
Status: Authorization result.

Above the table, you can enable the Hide IP Duplicates option to group entries by unique email + IP pairs and hide repeated entries.

Blocked clients¶

On this page you can view a list of clients who are temporarily blocked because of, for example, exceeded login attempts limit, etc. (refer to Settings for details). You can unblock these clients here.

Client ID: Client identifier in the system.
Client email: Email address of the client.
IP: IP address from which the client logged in to the system.
Blocked at: Date and time of blocking.
Expired at: Date and time of blocking expiration.
Reason: Reason for blocking.

Black lists¶

Black lists prohibit certain URLs for certain IP addresses. This functionality can be used to quickly block attackers at the application level.

Important

Blacklisting is an emergency measure and is not as reliable as blocking attackers at the server level. Contact your system administrators.

In this subsection you can view all existing black lists.

ID: Black list identifier in the system.
Route: URL access to which is prohibited.
IP: Blacklisted IP address(es) or subnet mask.
Active: Black list status.
Comment: Reason for blacklisting.
Created at: Date and time of the black list creation.
Updated at: Date and time of the black list update.

White lists¶

White lists can be used to restrict access to a specific URLs. Access will be allowed only from the listed IP addresses.

In this subsection you can view all existing white lists.

ID: White list identifier in the system.
Route: URL access to which is granted.
IP: Whitelisted IP address(es) or subnet mask.
Active: White list status.
Comment: Reason for whitelisting.
Created at: Date and time of the white list creation.
Updated at: Date and time of the white list update.

Transaction monitoring¶

In this subsection you can check transactions of your clients and see the risk scores, where the money came from, and all key signals about it:

Client ID: Identifier of the user, who created the transaction.
Transaction ID: Identifier of the transaction.
Transaction Type: Deposit or withdraw.
Created date: Date and time of the transaction.
Email: Email of the client.
Source amount: Transaction amount in the source currency.
Source currency: Transaction currency.
Provider: Name of the risk monitoring provider, SumSubstance available at the moment.
Review Result: Transaction check result by provider: red, green, or error.
Risk Score: Risk score of the transaction by provider.

To see details, click the edit button. Detailed info contains additional signals of the transaction such as where the funds came from, is there any risk that they were stolen, ML risk level of the exchange, etc.

Address whitelist¶

In this subsection you can see a list of wallet addresses for payouts, which clients added to white list.

Client ID: Identifier of the client who added the address.
Client Email: Email of the client who added the address.
Address: Address of the wallet.
Destination tag: Applicable for XRP, XLM, BNB, XEM.
Currency: Destination currency

Antifraud¶

The Antifraud section provides you with an opportunity to set up antifraud alerts and related procedures.

Antifraud notifications¶

On this page you can view a list of all antifraud notifications on events for which your email is set as a notification email.

ID: Notification identifier.
Client ID: Identifier of the client related to the notification.
Responsibles: Emails of admin users who are responsible for this antifraud procedure.
Type: Type of event which triggered the notification.
Date: Date and time of notification.
Client Name: Name of the client related to the notification.
Client Type: Type of the client related to the notification: individual, corporate, pro.
Client Internal Type: This field is used for internal purposes only.
Client Verification Level: Verification level of the client related to the notification.
Client Status: Status of the client related to the notification, refer to Client statuses for details.
Client Email: Email of the client related to the notification.
Client Last Login: Date and time of the client last log in to the system.
Status: If there are any Antifraud procedures related to this event, its status will be displayed here.
Closing Date: Date and time of event resolution.

To see details, click the edit button. Detailed info contains:

Main Info

Same as displayed in the notifications list.

Details

Violated or urgent parameters of the event, that triggered the notification.

Procedures of Notification

Steps that must be performed to resolve the event (refer to Antifraud procedures for details):

Priority: Step sequence number.
Status: Current status of the step: To Do, In Progress, Done.
Responsibles: Emails list of the Back Office users who are responsible for this step.
Last Update: Date and time of the last step update.
Last User Update: User who performed the last update.

Status Change

A list of event statuses updates.

Antifraud settings¶

The following antifraud events are supported:

Identical IP Used By Multiple Accounts: Someone logged in from the same IP address for the period specified in the settings.
Multiple Withdrawals with No Trading Activity: Withdrawal attempt by a client who does not trade.
Identical Withdrawal Wallet Address Used By Multiple Accounts: Withdrawals to the same wallet were made by other clients.
Identical Phone Number Used By Multiple Accounts: Other client has verified this phone number.
Identical Email Used By Multiple Accounts: The same email address has been ever used by another client.
Excessive Deposits Sum: The total amount of the client’s deposits exceeds the amount specified in the settings (in EUR).
Frequent Deposits: Once a day checks if the number of deposits has exceeded the limit specified in the settings for the selected period.
Verification Level Unauthorised Change: Admin whose email is not listed in the Exceptions has changed the verification level.
Excessive B2Trader Trades Amount: The number of trades for the specified period exceeds the limit specified in the settings, applicable only for B2Core and B2Trader solution.
B2Trader Arbitrage Triangle: The client has exceeded the arbitration triangle limit for the selected period, applicable only for B2Core and B2Trader solution.

For each event you can set:

Exceptions: A list of IPs or emails to which the selected event is not applied (notification is not triggered). Patterns of email addresses are supported. For example, if the exception rule is created for user*@email.com, the antifraud system will not be triggered for any address which starts with user and ends with @email.com like user+1@email.com, etc.
Notifications emails: Only registered users of the Back Office.
Settings: Available for most of the events: specify the trigger, for example, max deposit amount for a period. Setting options depend on the event type.

Antifraud procedures¶

For each notification you can configure a procedure, which describes the order of steps (actions) that must be performed to resolve this event.

In this subsection you can view all set procedures for all type of events.

ID: Procedure identifier in the system.
Notification Type: Event type.
Caption: Procedure description.
Responsibles: Emails list of the Back Office users who are responsible for this step.
Priority: Sequence number of the step.

After configuration, responsible administrators will be able to see the steps of the procedure in the details of the notifications, which are related to the procedure events, and change statuses after completing these steps.

References¶

Client statuses¶

Active — normal state, client can log in to the B2Core UI
Inactive — registration problems, client cannot log in to the B2Core UI
Banned — client is prohibited to log in to the B2Core UI

Client request statuses¶

Pending — request was sent but has not yet been processed by the administrator
Approved — request was approved by the administrator
Rejected — request was rejected by the administrator

Transaction statuses¶

Below are listed available statuses of financial operations: deposits, payouts, transfers, and exchanges.

New — transaction was created but has not yet been processed
Pending — transaction request was sent but has not yet been approved by the administrator
Done — transaction was successfully processed
Partial — transaction processing was not finished due to some technical problems
Failed — transaction failed due to incorrect parameters
Rejected — transaction request was rejected by the administrator
Canceled — transaction was canceled by the client
Success — deposit was credited
In progress — transaction is being processed
Hold failed — error occurred while debiting funds which were blocked (applicable if holds were enabled — refer to Operation types for details)

Currency codes¶

FIAT

Code	Alpha	Precision	Name
8	ALL	2	Albanian lek
12	DZD	2	Algerian dinar
32	ARS	2	Argentine peso
36	AUD	2	Australian dollar
44	BSD	2	Bahamian dollar
48	BHD	3	Bahraini dinar
50	BDT	2	Bangladeshi taka
51	AMD	2	Armenian dram
52	BBD	2	Barbados dollar
60	BMD	2	Bermudian dollar
64	BTN	2	Bhutanese ngultrum
68	BOB	2	Boliviano
72	BWP	2	Botswana pula
84	BZD	2	Belize dollar
90	SBD	2	Solomon Islands dollar
96	BND	2	Brunei dollar
104	MMK	2	Myanmar kyat
108	BIF	0	Burundian franc
116	KHR	2	Cambodian riel
124	CAD	2	Canadian dollar
132	CVE	0	Cape Verde escudo
136	KYD	2	Cayman Islands dollar
144	LKR	2	Sri Lankan rupee
152	CLP	0	Chilean peso
156	CNY (alias: CNH)	2	Chinese yuan
170	COP	2	Colombian peso
174	KMF	0	Comoro franc
188	CRC	2	Costa Rican colon
191	HRK	2	Croatian kuna
192	CUP	2	Cuban peso
203	CZK	2	Czech koruna
208	DKK	2	Danish krone
214	DOP	2	Dominican peso
222	SVC	2	Salvadoran colón
230	ETB	2	Ethiopian birr
232	ERN	2	Eritrean nakfa
238	FKP	2	Falkland Islands pound
242	FJD	2	Fiji dollar
262	DJF	0	Djiboutian franc
270	GMD	2	Gambian dalasi
292	GIP	2	Gibraltar pound
320	GTQ	2	Guatemalan quetzal
324	GNF	0	Guinean franc
328	GYD	2	Guyanese dollar
332	HTG	2	Haitian gourde
340	HNL	2	Honduran lempira
344	HKD	2	Hong Kong dollar
348	HUF	2	Hungarian forint
352	ISK	0	Icelandic króna
356	INR	2	Indian rupee
360	IDR	2	Indonesian rupiah
364	IRR	2	Iranian rial
365	IRT	2	Iranian Toman
368	IQD	3	Iraqi dinar
376	ILS	2	Israeli new shekel
388	JMD	2	Jamaican dollar
392	JPY	0	Japanese yen
398	KZT	2	Kazakhstani tenge
400	JOD	3	Jordanian dinar
404	KES	2	Kenyan shilling
408	KPW	2	North Korean won
410	KRW	0	South Korean won
414	KWD	3	Kuwaiti dinar
417	KGS	2	Kyrgyzstani som
418	LAK	2	Lao kip
422	LBP	2	Lebanese pound
426	LSL	2	Lesotho loti
430	LRD	2	Liberian dollar
434	LYD	3	Libyan dinar
440	LTL	2	Lithuanian Litas
446	MOP	2	Macanese pataca
454	MWK	2	Malawian kwacha
458	MYR	2	Malaysian ringgit
462	MVR	2	Maldivian rufiyaa
478	MRO	1	Mauritanian ouguiya
480	MUR	2	Mauritian rupee
484	MXN	2	Mexican peso
496	MNT	2	Mongolian tögrög
498	MDL	2	Moldovan leu
504	MAD	2	Moroccan dirham
512	OMR	3	Omani rial
516	NAD	2	Namibian dollar
524	NPR	2	Nepalese rupee
532	ANG	2	Netherlands Antillean guilder
533	AWG	2	Aruban florin
548	VUV	0	Vanuatu vatu
554	NZD	2	New Zealand dollar
558	NIO	2	Nicaraguan córdoba
566	NGN	2	Nigerian naira
578	NOK	2	Norwegian krone
586	PKR	2	Pakistani rupee
590	PAB	2	Panamanian balboa
598	PGK	2	Papua New Guinean kina
600	PYG	0	Paraguayan guaraní
604	PEN	2	Peruvian Sol
608	PHP	2	Philippine peso
634	QAR	2	Qatari riyal
643	RUB	2	Russian ruble
646	RWF	0	Rwandan franc
654	SHP	2	Saint Helena pound
678	STD	2	São Tomé and Príncipe dobra
682	SAR	2	Saudi riyal
690	SCR	2	Seychelles rupee
694	SLL	2	Sierra Leonean leone
702	SGD	2	Singapore dollar
704	VND	0	Vietnamese đồng
706	SOS	2	Somali shilling
710	ZAR	2	South African rand
728	SSP	2	South Sudanese pound
748	SZL	2	Swazi lilangeni
752	SEK	2	Swedish krona/kronor
756	CHF	2	Swiss franc
760	SYP	2	Syrian pound
764	THB	2	Thai baht
776	TOP	2	Tongan pa’anga
780	TTD	2	Trinidad and Tobago dollar
784	AED	2	United Arab Emirates dirham
788	TND	3	Tunisian dinar
800	UGX	0	Ugandan shilling
807	MKD	2	Macedonian denar
810	RUR	2	Russian ruble
818	EGP	2	Egyptian pound
826	GBP	2	Pound sterling
834	TZS	2	Tanzanian shilling
840	USD	2	United States dollar
858	UYU	2	Uruguayan peso
860	UZS	2	Uzbekistan som
882	WST	2	Samoan tala
886	YER	2	Yemeni rial
901	TWD	2	New Taiwan dollar
931	CUC	2	Cuban convertible peso
932	ZWL	2	Zimbabwean dollarA/10
933	BYN	2	Belarusian ruble
934	TMT	2	Turkmenistan manat
936	GHS	2	Ghanaian cedi
937	VEF	2	Venezuelan bolívar
938	SDG	2	Sudanese pound
940	UYI	0	Uruguay Peso en Unidades Indexadas (URUIURUI) (funds code)
941	RSD	2	Serbian dinar
943	MZN	2	Mozambican metical
944	AZN	2	Azerbaijani manat
946	RON	2	Romanian leu
947	CHE	2	WIR Euro (complementary currency)
948	CHW	2	WIR Franc (complementary currency)
949	TRY	2	Turkish lira
950	XAF	0	CFA franc BEAC
951	XCD	2	East Caribbean dollar
952	XOF	0	CFA franc BCEAO
953	XPF	0	CFP franc (franc Pacifique)
955	XBA		European Composite Unit(EURCO) (bond market unit)
956	XBB		European Monetary Unit (E.M.U.-6) (bond market unit)
957	XBC		European Unit of Account 9(E.U.A.-9) (bond market unit)
958	XBD		European Unit of Account 17(E.U.A.-17) (bond market unit)
959	XAU	2	Gold (one troy ounce)
960	XDR		Special drawing rights
961	XAG	3	Silver (one troy ounce)
962	XPT	2	Platinum (one troy ounce)
963	XTS		Code reserved for testing purposes
964	XPD	2	Palladium (one troy ounce)
965	XUA		ADB Unit of Account
967	ZMW	2	Zambian kwacha
968	SRD	2	Surinamese dollar
969	MGA	1	Malagasy ariary
970	COU	2	Unidad de Valor Real (UVR) (funds code)[7]
971	AFN	2	Afghan afghani
972	TJS	2	Tajikistani somoni
973	AOA	2	Angolan kwanza
975	BGN	2	Bulgarian lev
976	CDF	2	Congolese franc
977	BAM	2	Bosnia and Herzegovina convertible mark
978	EUR	2	Euro
979	MXV	2	Mexican Unidad de Inversion (UDI) (funds code)
980	UAH	2	Ukrainian hryvnia
981	GEL	2	Georgian lari
984	BOV	2	Bolivian Mvdol (funds code)
985	PLN	2	Polish złoty
986	BRL	2	Brazilian real
990	CLF	4	Unidad de Fomento (funds code)
994	XSU		SUCRE
997	USN	2	United States dollar (next day) (funds code)
999	XXX		No currency

Crypto

Code	Alpha	Precision	Name
1000	BTC (alias: XBT)	8	Bitcoin
1002	ETH	18	Ethereum
1003	LTC	8	Litecoin
1004	ETC	8	Ethereum Classic
1005	DASH (alias: DSH)	8	DASH
1006	BCH	8	Bitcoin Cash
1007	XMR	8	Monero
1009	PZM	8	Prizm
1010	XRP	6	Ripple
1012	XEM	8	XEM
1015	TFT	8	ThreeFold Token
1018	ADA	8	ADA
1019	DOGE	8	Dogecoin
1020	ZEC	8	Zcach
1021	XLM	7	Stellar
1022	EOS	8	EOS
1023	BWK	8	Bulwark
1025	NSD	8	Nasdacoin
1026	TRX	8	Tron
1027	FUT	8	FutPlayCoin
1029	MPC	8	MediaPlayCash
1995	XTZ	8	Tezos
1996	WAVES	8	Waves
1997	ICX	8	Icon
1999	BSV	8	Bitcoin SV
2000	B2B (alias: B2BX)	18	B2BX
2005	USDT	8	Tether
2006	EURT	8	Tether EUR
2007	R	8	Revain
2008	OMG	8	OmiseGO
2009	IOST	8	IOSToken
2010	VIU	8	Viuly
2011	EOS Token	8	EOS Token
2012	SRNT	18	Serenity
2014	NEO	8	NEO
2016	BXN	8	BITTXN
2018	DTC	8	DateCoin
2020	OLXA	2	OLXA
2021	PAX	8	PAX
2022	TUSD	8	TrueUSD
2023	GUSD	8	Gemini Dollar
2024	USDC	8	USD Coin
2025	BNB	8	Binance Coin
2030	XGT	8	XGT
2032	HDP	4	HedPay
2033	NADM	8	NeoAdam
2034	NOAH	18	NOAHCOIN
2035	TC	8	Titan Coin
2036	GGC	18	GG World Lottery
2037	SIM	18	Simmitri
2038	CTC	18	Catholic Coin
2039	MYX	8	Myoho
2040	CRAFTR	18	CraftR
2041	XRX	8	Global Property Register
2042	USDQ	18	USDQ
2043	ELLEX	18	Ellex Coin
2044	ANX	8	COINANX
2045	BNX	8	BTCNEXT Coin
2046	BFCL	18	BFCL Token
2047	ERN	8	EURON
2048	NWX	8	NIWIX Token
2049	C3W	8	C3 Wallet
2050	QDAO	18	Q DAO
2051	SPD	18	SPINDLE
2053	ZTX	18	Zulu Republic Token
2054	ITM	8	ITADAKI-MASU Coin
2055	DEC	8	Darico Ecosystem Coin
2056	KRWQ	8	KRWQ Stablecoin by Q DAO v1.0
2057	NZE	8	Nagezeni
2058	NIOX	8	NIOX
2060	VEST	8	VestChain
2061	BKZ	8	Bitkruz Token
2066	FMT	8	Free Market Token
2068	DAI	8	Dai Stablecoin
2070	AZ	8	AZ Token
2071	B21	8	B21 Token
2075	PDATA	8	PDATA
2077	BUSD	8	Binance USD
2078	ZVC	8	Zeven Coin
2081	ARBIS	8	ARBIS
2083	BII	8	Bitcoin 2
2084	BDS	8	Bitcoin Dollar Stable
2086	BWON	8	Bitcoin BWON
2087	BYUN	8	Bitcoin BYUN
2088	NEX	8	NEX
2090	TEX	8	TEX
2968	COVIP	8	COVIP
2969	SCAMUNKNOWN	8	Scam ALERT: UNKNOWN status. Audit made by Q DeFi Rating
2970	SCAMMEDIUMRISK	8	Scam ALERT: Medium Risk. Audit made by Q DeFi Rating
2971	SCAMHIGH	8	Scam ALERT: HIGH probability. Audit made by Q DeFi Rating
2972	NOAHARK	8	NOAH’s DeFi ARK v.1 Governance Token
2973	FLR	8	Spark
2974	FXRP	8	Spark
2975	XYM	8	XYM
2976	QDEFI	8	Q DeFi Rating & Governance token v2.0 Token
2977	T34	8	Platinum Software TECHNOLOGIES
2978	CNYQ	8	CNYQ Stablecoin by Q DAO
2979	JPYQ	8	JPYQ Stablecoin by Q DAO
2980	MILK2	8	MILK2 Coin
2981	SHAKE	8	SHAKE Coin
2982	MATIC	8	Matic Network
2983	ERG	8	Ergo
2984	LTCP	8	Litecoin PoS
2985	ZRX	8	0x
2986	BIP	8	Minter
2987	ATOM	8	Cosmos
2988	GRAM	8	Telegram Open Network IOU
2989	JPYQ	8	JPYQ
2990	NOAHP	8	NOAH.platinum
2991	CC	8	Custom Coin
2993	SPD	8	Spindle
2994	OWC	8	ODUWA Coin
2995	NCER	0	NIWIX Certificate
2996	NWX	8	NIWIX Token
2997	ERN	8	EURON
2998	BFCL	8	BFCL Token
2999	ABBC	8	ABBC

Block explorer list¶

Coins

Currency	Block explorer link
BCH	https://blockchair.com/bitcoin-cash/transaction/{address}
BNB-BSC	https://bscscan.com/tx/{address}
BNB-DEX	https://binance.mintscan.io/txs/{address}
BTC	https://www.blockchain.com/btc/tx/{address}
DASH	https://live.blockcypher.com/dash/tx/{address}
DOGE	https://live.blockcypher.com/doge/tx/{address}
ETH	https://etherscan.io/tx/{address}
LTC	https://live.blockcypher.com/ltc/tx/{address}
TRX	https://tronscan.org/#/transaction/{address}
XLM	https://stellarchain.io/tx/{address}
XMR	https://blockchair.com/monero/transaction/{address}
XRP	https://xrpscan.com/tx/{address}
ZEC	https://explorer.zcha.in/transactions/{address}

Stablecoins

Currency	Block explorer link
BUSD-BSC	https://bscscan.com/tx/{address}
BUSD-ETH	https://etherscan.io/tx/{address}
BUSD-T-BSC	https://bscscan.com/tx/{address}
DAI-BSC	https://bscscan.com/tx/{address}
DAI-ETH	https://etherscan.io/tx/{address}
TUSD-ETH	https://etherscan.io/tx/{address}
USDC-BSC	https://bscscan.com/tx/{address}
USDC-ETH	https://etherscan.io/tx/{address}
USDC-TRX	https://tronscan.org/#/transaction/{address}
USDP-BSC	https://bscscan.com/tx/{address}
USDP-ETH	https://etherscan.io/tx/{address}
USDT-ETH	https://etherscan.io/tx/{address}
USDT-TRX	https://tronscan.org/#/transaction/{address}
UST-BSC	https://bscscan.com/tx/{address}
UST-ETH	https://etherscan.io/tx/{address}

Tokens

Currency	Block explorer link
1INCH-BSC	https://bscscan.com/tx/{address}
1INCH-ETH	https://etherscan.io/tx/{address}
AAVE-ETH	https://etherscan.io/tx/{address}
AKRO-ETH	https://etherscan.io/tx/{address}
ALPHA-BSC	https://bscscan.com/tx/{address}
ALPHA-ETH	https://etherscan.io/tx/{address}
AMP-ETH	https://etherscan.io/tx/{address}
AXS-ETH	https://etherscan.io/tx/{address}
BADGER-ETH	https://etherscan.io/tx/{address}
BAL-ETH	https://etherscan.io/tx/{address}
BAND-BSC	https://bscscan.com/tx/{address}
BAND-ETH	https://etherscan.io/tx/{address}
BAT-BSC	https://bscscan.com/tx/{address}
BAT-ETH	https://etherscan.io/tx/{address}
BZRX-ETH	https://etherscan.io/tx/{address}
CAKE-BSC	https://bscscan.com/tx/{address}
CHR-ETH	https://etherscan.io/tx/{address}
CHZ-ETH	https://etherscan.io/tx/{address}
COMP-ETH	https://etherscan.io/tx/{address}
CRV-ETH	https://etherscan.io/tx/{address}
ENJ-ETH	https://etherscan.io/tx/{address}
FET-ETH	https://etherscan.io/tx/{address}
FTM-BSC	https://bscscan.com/tx/{address}
FTM-ETH	https://etherscan.io/tx/{address}
FTT-ETH	https://etherscan.io/tx/{address}
GRT-ETH	https://etherscan.io/tx/{address}
HOT-ETH	https://etherscan.io/tx/{address}
LINK-BSC	https://bscscan.com/tx/{address}
LINK-ETH	https://etherscan.io/tx/{address}
LRC-ETH	https://etherscan.io/tx/{address}
MANA-ETH	https://etherscan.io/tx/{address}
MATIC-ETH	https://etherscan.io/tx/{address}
MKR-BSC	https://bscscan.com/tx/{address}
MKR-ETH	https://etherscan.io/tx/{address}
NU-ETH	https://etherscan.io/tx/{address}
OCEAN-ETH	https://etherscan.io/tx/{address}
OMG-ETH	https://etherscan.io/tx/{address}
QNT-ETH	https://etherscan.io/tx/{address}
RARI-ETH	https://etherscan.io/tx/{address}
REEF-BSC	https://bscscan.com/tx/{address}
REEF-ETH	https://etherscan.io/tx/{address}
REN-ETH	https://etherscan.io/tx/{address}
RSR-ETH	https://etherscan.io/tx/{address}
SAND-ETH	https://etherscan.io/tx/{address}
SHIB-ETH	https://etherscan.io/tx/{address}
SNX-BSC	https://bscscan.com/tx/{address}
SNX-ETH	https://etherscan.io/tx/{address}
SRM-ETH	https://etherscan.io/tx/{address}
SUSHI-BSC	https://bscscan.com/tx/{address}
SUSHI-ETH	https://etherscan.io/tx/{address}
SXP-BSC	https://bscscan.com/tx/{address}
SXP-ETH	https://etherscan.io/tx/{address}
UNI-BSC	https://bscscan.com/tx/{address}
UNI-ETH	https://etherscan.io/tx/{address}
YFI-BSC	https://bscscan.com/tx/{address}
YFI-ETH	https://etherscan.io/tx/{address}
ZRX-ETH	https://etherscan.io/tx/{address}