Static deposit

Learn how static deposits work in B2CORE, their benefits over regular deposits, and how to manage unresolved deposit requests

Static deposits provide a reusable and persistent way for clients to fund their wallets in B2CORE. Unlike regular one-time deposits, static deposits allow clients to use the same static payment details (also called identities) multiple times, eliminating the need to generate new payment pages with payment details for each transaction.

Currently, the B2BINPAY v3 and Coinsbuy v3 payment systems can be configured to use static payment details. for details, refer to How to integrate B2BINPAY.

Difference between regular deposits and static deposits

Regular deposits

A regular deposit is a one-time transaction initiated by a client. Each deposit requires generating a new, temporary payment page with payment details.

The process for regular deposits is as follows:

On the Deposit page in the B2CORE UI, the client selects their wallet, deposit currency, specifies the deposit amount, and chooses an available deposit method.
The client fills in the required additional fields, depending on the selected method.
After initiating the deposit, the client is redirected to a payment page or shown a QR code. The page has an expiration time.
Once the deposit is completed or expires, the payment page and its payment details can't be reused.

Static deposit

A static deposit uses persistent payment details generated by a client. These details remain available for repeated use and are permanently associated with that client.

This approach is especially useful for crypto and bank payments, where clients may want to reuse the same crypto address or bank requisites for multiple deposits.

The process for static deposits is as follows:

On the Deposit page in the B2CORE UI, the client selects their wallet, deposit currency, and chooses a deposit method that supports static deposits.
The client fills in the required additional fields, depending on the selected method, and generates payment details (for example, a crypto address or bank requisites).
The generated payment details are saved and can be reused for future deposits with different amounts.
The payment details don't expire and remain active as long as they exist within the selected payment system.

Key points

Static payment details can be reused multiple times to deposit different amounts.
Each set of payment details is permanently associated with a specific client.
Payment details don't expire and remain valid unless explicitly deactivated.
Multiple payment details can be generated for the same payment method, allowing the client to choose which one to use.

Unresolved requests

On this page, you can view a list of unresolved requests that are created when issues occur during static deposit processing and the static deposit fails to be created. These requests allow the admin to track errors, identify their causes, and take actions to resolve static deposit issues.

The following information is provided about each unresolved request:

General information

The unique identifier of the unresolved request.

Status

The request status:

Unresolved — indicates that the static deposit couldn't be created and an unresolved request was generated.
Resolved — indicates that the request was reviewed and manually resolved by the admin.

Error code

The reason why the unresolved request was created. The table below lists possible error codes related to static deposit processing, along with their causes and configuration scenarios in which they may occur.

Error name	Error code	Description	Comments
IdentityNotFound	`static_deposit.identity.not_found`	The payment details aren't found in B2CORE but exist in the Payment System Service (PSS).	Occurs when a static deposit is created in PSS, but the payment details associated with the static deposit are missing in B2CORE.
IdentityArchived	`static_deposit.identity.archived`	The payment details associated with a static deposit are archived.	Contact support and provide the error code and request details.
OperationNotAvailable	`static_deposit.operation.not_available`	The `deposit` operation type is disabled in B2CORE Back Office.	Occurs when deposits aren't allowed because the `deposit` operation type is disabled in System > Operation types.
ClientNotFound	`static_deposit.client.not_found`	The client associated with the payment details isn't found.	Contact support and provide the error code and request details.
ClientNotActive	`static_deposit.client.not_active`	The client associated with the payment details isn't active.	Occurs when the status of a client profile is Banned or Inactive.
MethodNotAvailable	`static_deposit.method.not_available`	The deposit method associated with the the payment details is unavailable.	Occurs when the deposit method is disabled or restricted for the client.
AccountNotFound	`static_deposit.account.not_found`	The client account associated with the payment details isn't found.	Contact support and provide the error code and request details.
AccountArchived	`static_deposit.account.archived`	The client account associated with the payment details is archived.	Occurs when the client account is archived in B2CORE.
AccountInsufficientRights	`static_deposit.account.insufficient_rights`	The client doesn't have permission to perform deposits, or the client account is restricted from deposits.	Occurs when deposit permissions are disable for the client or for the client account.
CurrencyNotFound	`static_deposit.currency.not_found`	The currency associated with the payment details ins't found in B2CORE.	Occurs when the currency associated with the payment details is disabled or missing in Currencies > Currencies.
AccountCurrencyNotSupported	`static_deposit.account.currency_not_supported`	The account currency isn't supported by the deposit method.	Occurs when the currency in which the client account is denominated isn't listed in the Available account currencies field in the deposit method details.
MethodCurrencyNotSupported	`static_deposit.method.currency_not_supported`	The operation currency isn't supported by the deposit method.	Occurs when the currency in which a static deposit must be processed isn't listed on the PS Currencies tab in the deposit method details.
IdentityCurrencyMismatch	`static_deposit.identity.currency_mismatch`	The operation currency doesn't match the currency associated with the payment details.	Occurs when the currency of a static deposit is different from the currency associated with the payment details.
AmountInvalid	`static_deposit.amount.invalid`	The deposit amount is invalid.	Occurs when the amount of a static deposit is missing, non-numeric, zero, or negative.
ExchangeRateProviderError	`static_deposit.exchange.rate_provider_error`	The exchange rate can't be retrieved.	Occurs when a static deposit requires currency conversion but the required currency pair isn't configured in Currencies > Rates.

Creation date

The date and time when the request was created.

To view the request details, click the eye icon.

Details

The details page displays extended information about the static deposit and the related error. Once the issue has been addressed, the request can be manually closed by clicking the Resolve button.