Header Image
Information about the availability of the BVNK Crypto Payments services.

Ethereum (ETH)




Operational

Tether USD (USDT-ERC20)




Operational

USD Coin (USDC-ERC20)




Operational

Dai (DAI-ERC20)




Operational

PayPal USD (PYUSD-ERC20)




Operational

Shiba Inu (SHIB-ERC20)




Operational

First Digital USD (FDUSD-ERC20)




Operational

Tronix (TRX)




Operational

Tether USD (USDT-TRC20)




Operational

Binance Coin (BNB)




Operational

Tether USD (USDT-BEP20)




Operational

USD Coin (USDC-BEP20)




Operational

Shiba Inu (SHIB-BEP20)




Operational

First Digital USD (FDUSD-BEP20)




Operational

Tether USD (USDT-POLYGON)




Operational

USD Coin (USDC-POLYGON)




Operational

Polygon (POL-POLYGON)




Operational

Cardano (ADA)




Operational

Algorand (ALGO)




Operational

Bitcoin (BTC)




Operational

BitcoinCash (BCH)




Operational

Dogecoin (DOGE)




Operational

Litecoin (LTC)




Operational

Ripple (XRP)




Operational

Solana (SOL)




Operational

Wallets




Operational

Scheduled Maintenance

Schedule

September 27, 2026 09:00 - 10:30 UTC

Components

Ethereum (ETH), Tether USD (USDT-ERC20), USD Coin (USDC-ERC20), Dai (DAI-ERC20), PayPal USD (PYUSD-ERC20), Shiba Inu (SHIB-ERC20), First Digital USD (FDUSD-ERC20), Tronix (TRX), Tether USD (USDT-TRC20), Binance Coin (BNB), Tether USD (USDT-BEP20), USD Coin (USDC-BEP20), Shiba Inu (SHIB-BEP20), First Digital USD (FDUSD-BEP20), Tether USD (USDT-POLYGON), USD Coin (USDC-POLYGON), Polygon (POL-POLYGON), Cardano (ADA), Algorand (ALGO), Bitcoin (BTC), BitcoinCash (BCH), Dogecoin (DOGE), Litecoin (LTC), Ripple (XRP), Solana (SOL), Wallets

Service

Crypto Payins, Crypto Payouts, BVNK Portal

Description

Dear customer, We are writing to inform you of scheduled maintenance to BVNK’s infrastructure on Sunday, 27 September 2026. During the maintenance window, our transaction screening services will be intermittently unavailable. As screening is required for all transactions, sending or receiving fiat or crypto might be delayed. Immediately following completion of the update, all systems will resume normal processing. Maintenance details: Date: Sunday, 27 September 2026 Time: Approximately 09:00–10:30 CET Impact: All incoming and outgoing fiat and crypto transactions can be delayed. No action is required from your side. Please reach out to merchants@bvnk.com, if you have any questions. Thank you for your continued partnership. Kind regards, Team BVNK

History (Last 7 days)

Incident Status

Degraded Performance


Components

Ethereum (ETH), Tether USD (USDT-ERC20), USD Coin (USDC-ERC20), Dai (DAI-ERC20), PayPal USD (PYUSD-ERC20), Shiba Inu (SHIB-ERC20), First Digital USD (FDUSD-ERC20), Tronix (TRX), Tether USD (USDT-TRC20), Binance Coin (BNB), Tether USD (USDT-BEP20), USD Coin (USDC-BEP20), Shiba Inu (SHIB-BEP20), First Digital USD (FDUSD-BEP20), Tether USD (USDT-POLYGON), USD Coin (USDC-POLYGON), Polygon (POL-POLYGON), Cardano (ADA), Algorand (ALGO), Bitcoin (BTC), BitcoinCash (BCH), Dogecoin (DOGE), Ripple (XRP), Solana (SOL)


Service

Crypto Payins, Crypto Payouts




September 22, 2026 15:41 UTC
RESOLVED

The issue causing intermittent crypto processing delays has been resolved. We apologize for the disruption and appreciate your patience during this time.

September 22, 2026 11:43 UTC
INVESTIGATING

Our team is investigating an issue affecting the processing of crypto transactions. Our team is working around the clock to find a solution. Thank you for your patience. Next update at 13:00 UTC

Incident Status

Operational


Components

Wallets


Service

BVNK Portal




September 22, 2026 15:37 UTC
RESOLVED

The issue affecting Fiat Swift Ref errors has been resolved. We apologize for the disruption and appreciate your patience during this time.

July 27, 2026 11:20 UTC
MONITORING


July 27, 2026 11:19 UTC
RESOLVED

We have resolved an issue affecting crypto payment creation via the Merchant Portal, where customers may have received an error when attempting to create a Crypto payment & Channel. We appreciate your patience and understanding while we worked to restore functionality. We apologize for any inconvenience caused.

July 17, 2026 15:12 UTC
MONITORING

We have resolved the issue affecting FIAT pay ins & FIAT payouts and are closely monitoring the system to ensure full recovery and stability. Thank you for your patience.

July 1, 2026 14:41 UTC
MONITORING

We have received confirmation that the affected BIC, SYPLMTM2XXX, has now been successfully republished in the latest SWIFTRef publication. As a next step, we are asking impacted customers to retry beneficiary creation and/or payment initiation. This will allow us to verify that the updated SWIFTRef data has propagated successfully across the relevant banking and payment service provider networks. Our teams will continue to monitor the situation closely and gather customer feedback to confirm full resolution before formally closing this incident. Thank you for your patience and understanding throughout this matter. Further updates will be provided as required.

June 11, 2026 15:50 UTC
IDENTIFIED

Update: Temporary SWIFTRef Data Issue Impacting addition and validation of EUR SEPA beneficiaries We are currently aware of an ongoing issue affecting how our Maltese BIC (SYPLMTM2XXX) has been displayed within the SWIFTRef reference data service. Current Status: - Our BIC remains active and fully operational - SWIFTRef has corrected the reference data, and SYPLMTM2XXX is now shown as active and published on BWO as of 9 June 2026 - SWIFT issued a broadcast on 10 June 2026 notifying the SWIFT community that BIC SYPLMTM2XXX is active and requesting participants to update their records accordingly - There is no impact to EUR funds already sent or successfully executed transactions Potential ongoing impact: - Some customers may experience temporary issues when adding or validating EUR SEPA beneficiaries. In such cases, we kindly ask customers to contact their bank or payment provider and request that they refresh their SWIFTRef reference data to reflect our active BIC - EUR payment setup or beneficiary validation may be delayed or temporarily rejected until the remitting banks and payment providers databases are updated with the correct information We continue to actively monitor the situation closely, working with our counterparties and will provide further updates when possible.

June 9, 2026 14:44 UTC
IDENTIFIED

We are currently aware of an ongoing issue affecting how our Maltese BIC (SYPLMTM2XXX) has been displayed within the SWIFTRef reference data service. Current Status: - Our BIC remains active and fully operational - SWIFTRef has corrected the reference data, and SYPLMTM2XXX is now shown as active and published on BWO as of 9 June 2026 - There is no impact to EUR funds already sent or successfully executed transactions Potential ongoing impact: - Some customers may experience temporary issues when adding or validating EUR SEPA beneficiaries. In such cases, we kindly ask customers to contact their bank or payment provider and request that they refresh their SWIFTRef reference data to reflect our active BIC - EUR payment setup or beneficiary validation may be delayed or temporarily rejected until the remitting banks and payment providers databases are updated with the correct information We are actively monitoring the situation closely, working with our counterparties and will provide further updates when possible.

June 8, 2026 14:55 UTC
IDENTIFIED

We are currently experiencing an issue affecting how our Maltese BIC (SYPLMTM2XXX) is displayed in the SWIFTRef reference data service. Note: - Our BIC remains active and operational - We are aware that SWIFTRef is currently showing incorrect or outdated information - SWIFT has confirmed that the reference data will be corrected imminently - There is no impact to EUR funds or executed transactions Potential impact - Some customers may experience temporary issues when adding or validating EUR beneficiaries - EUR Payment setup or validation may be delayed or rejected We are actively working with SWIFT to ensure the data is corrected as quickly as possible. We expect the correction to be reflected shortly and will provide further updates..."