Update - La operativa de compra, venta, retirada y depósito de EURR y USDR permanece suspendida desde el 24 de mayo debido a un incidente de ciberseguridad en StablR Ltd., entidad emisora de ambos tokens y supervisada por la MFSA. Se trata de un incidente ajeno a la infraestructura de Bit2Me.
El 25 de agosto StablR publicó una nueva actualización con información adicional sobre el incidente. Los puntos principales, según el emisor:
- Un tercero externo no autorizado accedió a parte de su infraestructura los días 23 y 24 de mayo y acuñó tokens EURR y USDR fuera de su proceso de emisión autorizado.
- StablR indica que los tokens emitidos legítimamente siguen respaldados por reservas mantenidas en cuentas segregadas conforme a MiCAR.
- La investigación forense ha concluido y el emisor afirma haber implantado medidas de remediación. No se han producido nuevas emisiones no autorizadas.
- La suspensión de emisión y reembolso se mantiene. StablR trabaja con la MFSA en una reanudación ordenada del servicio, sin fecha comunicada por ahora.
Puedes consultar el comunicado completo en el sitio de StablR: https://stablr.com/insights/notification-update-25-08-2026
------
Buying, selling, withdrawal, and deposit operations for EURR and USDR have remained suspended since May 24 due to a cybersecurity incident at StablR Ltd., the issuing entity of both tokens and supervised by the MFSA. This is an incident unrelated to Bit2Me's infrastructure.
On August 25, StablR published a new update with additional information about the incident. The main points, according to the issuer:
- An unauthorized external third party gained access to part of its infrastructure on May 23 and 24 and minted EURR and USDR tokens outside its authorized issuance process.
- StablR states that legitimately issued tokens remain backed by reserves held in segregated accounts in accordance with MiCAR.
- The forensic investigation has concluded, and the issuer states it has implemented remediation measures. No new unauthorized issuances have occurred.
- The suspension of issuance and redemption remains in place. StablR is working with the MFSA toward an orderly resumption of service, with no date announced at this time.
You can read the full statement on StablR's website: https://stablr.com/insights/notification-update-25-08-2026
Aug 26, 2026 - 11:25 CEST
El 25 de agosto StablR publicó una nueva actualización con información adicional sobre el incidente. Los puntos principales, según el emisor:
- Un tercero externo no autorizado accedió a parte de su infraestructura los días 23 y 24 de mayo y acuñó tokens EURR y USDR fuera de su proceso de emisión autorizado.
- StablR indica que los tokens emitidos legítimamente siguen respaldados por reservas mantenidas en cuentas segregadas conforme a MiCAR.
- La investigación forense ha concluido y el emisor afirma haber implantado medidas de remediación. No se han producido nuevas emisiones no autorizadas.
- La suspensión de emisión y reembolso se mantiene. StablR trabaja con la MFSA en una reanudación ordenada del servicio, sin fecha comunicada por ahora.
Puedes consultar el comunicado completo en el sitio de StablR: https://stablr.com/insights/notification-update-25-08-2026
------
Buying, selling, withdrawal, and deposit operations for EURR and USDR have remained suspended since May 24 due to a cybersecurity incident at StablR Ltd., the issuing entity of both tokens and supervised by the MFSA. This is an incident unrelated to Bit2Me's infrastructure.
On August 25, StablR published a new update with additional information about the incident. The main points, according to the issuer:
- An unauthorized external third party gained access to part of its infrastructure on May 23 and 24 and minted EURR and USDR tokens outside its authorized issuance process.
- StablR states that legitimately issued tokens remain backed by reserves held in segregated accounts in accordance with MiCAR.
- The forensic investigation has concluded, and the issuer states it has implemented remediation measures. No new unauthorized issuances have occurred.
- The suspension of issuance and redemption remains in place. StablR is working with the MFSA toward an orderly resumption of service, with no date announced at this time.
You can read the full statement on StablR's website: https://stablr.com/insights/notification-update-25-08-2026
Aug 26, 2026 - 11:25 CEST
Update - Actualización — 29 de julio de 2026
Compartimos la última comunicación oficial publicada por StablR Ltd. en relación con el incidente de ciberseguridad detectado el pasado 24 de mayo.
StablR confirma que el incidente continúa contenido y que no se ha producido ninguna emisión no autorizada adicional desde la fecha del incidente. La suspensión temporal de la emisión y el canje de EURR y USDR se mantiene como parte del Plan de Recuperación activado por la compañía.
Puntos clave:
- Incidente contenido: No ha habido nueva actividad no autorizada. La suspensión de emisión y canje de EURR y USDR continúa en vigor como medida prevista en el Plan de Recuperación.
- Proceso de recuperación en curso: Durante los últimos dos meses, StablR ha trabajado de forma continuada en la investigación y el proceso de remediación, junto con especialistas externos en ciberseguridad, asesores legales y las autoridades competentes, incluida la Malta Financial Services Authority. Se han alcanzado avances significativos.
- Información limitada por integridad del proceso: Determinados aspectos del trabajo en curso —incluyendo elementos de la investigación, la interlocución con autoridades y los pasos técnicos y operativos— no pueden hacerse públicos en este momento. Esta decisión es deliberada y tiene por objeto proteger la integridad del proceso y los intereses de los titulares de tokens.
- Activos salvaguardados intactos: Todos los activos que respaldan EURR y USDR se mantienen en cuentas segregadas y fondos del mercado monetario, separados de los fondos propios de la compañía, de conformidad con MiCAR. Según la información disponible, los activos salvaguardados previos al incidente permanecen intactos.
- Aviso de fraude: Los titulares de tokens deben utilizar únicamente los canales oficiales de StablR. StablR nunca solicitará claves privadas, frases semilla, contraseñas ni ningún pago. Cualquier comunicación en ese sentido debe considerarse fraudulenta y reportarse.
Nota de Bit2Me
La gestión de este incidente y la ejecución del plan de recuperación corresponden íntegramente a StablR Ltd., entidad emisora de ambos tokens. La operativa en Bit2Me se reactivará en el momento en que StablR restablezca el servicio de forma segura.
Mantendremos esta página actualizada conforme el emisor publique nueva información oficial.
Gracias por tu paciencia y comprensión.
(Comunicado oficial de StablR: stablr.com/insights / Contacto: info@stablr.com)
Update — July 29, 2026
We share the latest official communication published by StablR Ltd. regarding the cybersecurity incident detected on May 24th.
StablR confirms that the incident remains contained and that there has been no further unauthorised issuance since the date of the incident. The temporary suspension of EURR and USDR minting and redemption remains in place as part of the Company's activated Recovery Plan.
Key points:
- Incident contained: There has been no further unauthorised activity. The suspension of EURR and USDR minting and redemption remains in place as provided for under the Recovery Plan.
- Recovery process underway: Over the past two months, StablR has been working relentlessly on the investigation and remediation process, together with external cybersecurity specialists, legal counsel, and the relevant authorities, including the Malta Financial Services Authority. Substantial progress has been made.
- Limited disclosure to protect process integrity: Certain aspects of the ongoing work — including elements of the investigation, engagement with authorities, and the technical and operational steps being taken — cannot be disclosed publicly at this time. This is a deliberate decision taken to protect the integrity of the ongoing process and the interests of token holders.
- Safeguarded assets remain intact: All assets backing EURR and USDR are held in segregated accounts and money market funds, separate from the Company's own funds, in accordance with MiCAR. On the basis of the information available to date, the safeguarded assets held prior to the incident remain intact.
- Fraud warning: Token holders are reminded to rely only on StablR's official channels. StablR will never contact you to request private keys, seed phrases, passwords, or any payment. Any such communication should be treated as fraudulent and reported.
Bit2Me Note
The management of this incident and the execution of the recovery plan correspond entirely to StablR Ltd., the issuing entity of both tokens. Operations on Bit2Me will be reactivated as soon as StablR safely restores the service.
We will keep this page updated as the issuer publishes new official information.
Thank you for your patience and understanding.
(Official statement from StablR: stablr.com/insights / Contact: info@stablr.com)
Jul 28, 2026 - 16:00 CEST
Compartimos la última comunicación oficial publicada por StablR Ltd. en relación con el incidente de ciberseguridad detectado el pasado 24 de mayo.
StablR confirma que el incidente continúa contenido y que no se ha producido ninguna emisión no autorizada adicional desde la fecha del incidente. La suspensión temporal de la emisión y el canje de EURR y USDR se mantiene como parte del Plan de Recuperación activado por la compañía.
Puntos clave:
- Incidente contenido: No ha habido nueva actividad no autorizada. La suspensión de emisión y canje de EURR y USDR continúa en vigor como medida prevista en el Plan de Recuperación.
- Proceso de recuperación en curso: Durante los últimos dos meses, StablR ha trabajado de forma continuada en la investigación y el proceso de remediación, junto con especialistas externos en ciberseguridad, asesores legales y las autoridades competentes, incluida la Malta Financial Services Authority. Se han alcanzado avances significativos.
- Información limitada por integridad del proceso: Determinados aspectos del trabajo en curso —incluyendo elementos de la investigación, la interlocución con autoridades y los pasos técnicos y operativos— no pueden hacerse públicos en este momento. Esta decisión es deliberada y tiene por objeto proteger la integridad del proceso y los intereses de los titulares de tokens.
- Activos salvaguardados intactos: Todos los activos que respaldan EURR y USDR se mantienen en cuentas segregadas y fondos del mercado monetario, separados de los fondos propios de la compañía, de conformidad con MiCAR. Según la información disponible, los activos salvaguardados previos al incidente permanecen intactos.
- Aviso de fraude: Los titulares de tokens deben utilizar únicamente los canales oficiales de StablR. StablR nunca solicitará claves privadas, frases semilla, contraseñas ni ningún pago. Cualquier comunicación en ese sentido debe considerarse fraudulenta y reportarse.
Nota de Bit2Me
La gestión de este incidente y la ejecución del plan de recuperación corresponden íntegramente a StablR Ltd., entidad emisora de ambos tokens. La operativa en Bit2Me se reactivará en el momento en que StablR restablezca el servicio de forma segura.
Mantendremos esta página actualizada conforme el emisor publique nueva información oficial.
Gracias por tu paciencia y comprensión.
(Comunicado oficial de StablR: stablr.com/insights / Contacto: info@stablr.com)
Update — July 29, 2026
We share the latest official communication published by StablR Ltd. regarding the cybersecurity incident detected on May 24th.
StablR confirms that the incident remains contained and that there has been no further unauthorised issuance since the date of the incident. The temporary suspension of EURR and USDR minting and redemption remains in place as part of the Company's activated Recovery Plan.
Key points:
- Incident contained: There has been no further unauthorised activity. The suspension of EURR and USDR minting and redemption remains in place as provided for under the Recovery Plan.
- Recovery process underway: Over the past two months, StablR has been working relentlessly on the investigation and remediation process, together with external cybersecurity specialists, legal counsel, and the relevant authorities, including the Malta Financial Services Authority. Substantial progress has been made.
- Limited disclosure to protect process integrity: Certain aspects of the ongoing work — including elements of the investigation, engagement with authorities, and the technical and operational steps being taken — cannot be disclosed publicly at this time. This is a deliberate decision taken to protect the integrity of the ongoing process and the interests of token holders.
- Safeguarded assets remain intact: All assets backing EURR and USDR are held in segregated accounts and money market funds, separate from the Company's own funds, in accordance with MiCAR. On the basis of the information available to date, the safeguarded assets held prior to the incident remain intact.
- Fraud warning: Token holders are reminded to rely only on StablR's official channels. StablR will never contact you to request private keys, seed phrases, passwords, or any payment. Any such communication should be treated as fraudulent and reported.
Bit2Me Note
The management of this incident and the execution of the recovery plan correspond entirely to StablR Ltd., the issuing entity of both tokens. Operations on Bit2Me will be reactivated as soon as StablR safely restores the service.
We will keep this page updated as the issuer publishes new official information.
Thank you for your patience and understanding.
(Official statement from StablR: stablr.com/insights / Contact: info@stablr.com)
Jul 28, 2026 - 16:00 CEST
Update - Actualización — 25 de junio de 2026
Compartimos la última comunicación oficial publicada por StablR Ltd. en relación con el incidente de ciberseguridad. La suspensión del minting y la redención de EURR y USDR se mantiene como medida de precaución. StablR confirma que no se han producido nuevas emisiones no autorizadas desde que se detectó el problema. La investigación sigue activa, coordinada con la Autoridad regulatoria (MFSA de Malta) y especialistas externos, en cumplimiento de MiCAR y DORA.
Puntos clave:
- Suspensión preventiva mantenida: El minting y la redención de EURR y USDR continúan suspendidos. No se han producido emisiones no autorizadas adicionales desde la detección del incidente.
- Investigación activa: Los trabajos se llevan a cabo de forma diligente y en estrecha coordinación con la Autoridad y con especialistas externos, conforme a las obligaciones de StablR bajo MiCAR y DORA. StablR no facilitará detalles del incidente mientras la investigación permanezca abierta.
- Alerta ante fraudes: StablR avisa a los holders de estar atentos ante posibles intentos de fraude. La información oficial se publica exclusivamente en los canales oficiales de StablR. StablR nunca solicitará claves privadas, seed phrases, contraseñas ni pagos de ningún tipo.
Nota de Bit2Me
La gestión de este incidente y la ejecución del plan de recuperación corresponden íntegramente a StablR Ltd., entidad emisora de ambos tokens. La operativa en Bit2Me se reactivará en el momento en que StablR restablezca el servicio de forma segura.
Mantendremos esta página actualizada conforme el emisor publique nueva información oficial.
Gracias por tu paciencia y comprensión.
(Comunicado oficial de StablR: stablr.com / Contacto: info@stablr.com)
---
Update — June 25, 2026
We share the latest official communication published by StablR Ltd. regarding the cybersecurity incident. The suspension of EURR and USDR minting and redemption remains in place as a precautionary measure. StablR confirms that no further unauthorised issuance has occurred since the incident was detected. The investigation remains active, carried out in close coordination with the Authority (MFSA of Malta) and external specialists, consistent with StablR's obligations under MiCAR and DORA.
Key points:
- Precautionary suspension maintained: Minting and redemption of EURR and USDR remain suspended. No further unauthorised issuance has occurred since the incident was detected.
- Active investigation: Work is being carried out diligently and in close coordination with the Authority and external specialists, in keeping with StablR's obligations under MiCAR and DORA. StablR will not share details of the investigation while it remains in progress.
- Fraud alert: StablR urges holders to stay alert to fraud attempts. Official information is published exclusively through StablR's official channels. StablR will never contact holders to request private keys, seed phrases, passwords or payment of any kind.
Bit2Me Note
The management of this incident and the execution of the recovery plan correspond entirely to StablR Ltd., the issuing entity of both tokens. Operations on Bit2Me will be reactivated as soon as StablR safely restores the service.
We will keep this page updated as the issuer publishes new official information.
Thank you for your patience and understanding.
(Official statement from StablR: stablr.com / Contact: info@stablr.com)
Jun 16, 2026 - 10:17 CEST
Compartimos la última comunicación oficial publicada por StablR Ltd. en relación con el incidente de ciberseguridad. La suspensión del minting y la redención de EURR y USDR se mantiene como medida de precaución. StablR confirma que no se han producido nuevas emisiones no autorizadas desde que se detectó el problema. La investigación sigue activa, coordinada con la Autoridad regulatoria (MFSA de Malta) y especialistas externos, en cumplimiento de MiCAR y DORA.
Puntos clave:
- Suspensión preventiva mantenida: El minting y la redención de EURR y USDR continúan suspendidos. No se han producido emisiones no autorizadas adicionales desde la detección del incidente.
- Investigación activa: Los trabajos se llevan a cabo de forma diligente y en estrecha coordinación con la Autoridad y con especialistas externos, conforme a las obligaciones de StablR bajo MiCAR y DORA. StablR no facilitará detalles del incidente mientras la investigación permanezca abierta.
- Alerta ante fraudes: StablR avisa a los holders de estar atentos ante posibles intentos de fraude. La información oficial se publica exclusivamente en los canales oficiales de StablR. StablR nunca solicitará claves privadas, seed phrases, contraseñas ni pagos de ningún tipo.
Nota de Bit2Me
La gestión de este incidente y la ejecución del plan de recuperación corresponden íntegramente a StablR Ltd., entidad emisora de ambos tokens. La operativa en Bit2Me se reactivará en el momento en que StablR restablezca el servicio de forma segura.
Mantendremos esta página actualizada conforme el emisor publique nueva información oficial.
Gracias por tu paciencia y comprensión.
(Comunicado oficial de StablR: stablr.com / Contacto: info@stablr.com)
---
Update — June 25, 2026
We share the latest official communication published by StablR Ltd. regarding the cybersecurity incident. The suspension of EURR and USDR minting and redemption remains in place as a precautionary measure. StablR confirms that no further unauthorised issuance has occurred since the incident was detected. The investigation remains active, carried out in close coordination with the Authority (MFSA of Malta) and external specialists, consistent with StablR's obligations under MiCAR and DORA.
Key points:
- Precautionary suspension maintained: Minting and redemption of EURR and USDR remain suspended. No further unauthorised issuance has occurred since the incident was detected.
- Active investigation: Work is being carried out diligently and in close coordination with the Authority and external specialists, in keeping with StablR's obligations under MiCAR and DORA. StablR will not share details of the investigation while it remains in progress.
- Fraud alert: StablR urges holders to stay alert to fraud attempts. Official information is published exclusively through StablR's official channels. StablR will never contact holders to request private keys, seed phrases, passwords or payment of any kind.
Bit2Me Note
The management of this incident and the execution of the recovery plan correspond entirely to StablR Ltd., the issuing entity of both tokens. Operations on Bit2Me will be reactivated as soon as StablR safely restores the service.
We will keep this page updated as the issuer publishes new official information.
Thank you for your patience and understanding.
(Official statement from StablR: stablr.com / Contact: info@stablr.com)
Jun 16, 2026 - 10:17 CEST
Update - Compartimos la última actualización oficial emitida por StablR Ltd. en relación con el incidente de ciberseguridad del pasado 24 de mayo. El emisor informa que continúa ejecutando su Plan de Recuperación en colaboración con la Autoridad de Servicios Financieros de Malta (MFSA), siendo la prioridad de la compañía: la protección de los poseedores de tokens, la integridad del proceso de recuperación y la evaluación ordenada de la situación para determinar los próximos pasos.
Puntos clave:
- Operativa suspendida: La emisión, canje, depósitos y retiradas de EURR y USDR se mantienen temporalmente suspendidos en todas las plataformas hasta nuevo aviso.
- Reservas seguras: StablR reitera que los activos de reserva que respaldan ambos tokens siguen estando completamente segregados y protegidos.
- Alerta de seguridad: Se recuerda a los usuarios confiar únicamente en canales oficiales. El emisor nunca solicitará claves privadas, contraseñas ni pagos.
Nota de Bit2Me
La gestión de este incidente y la ejecución del plan de recuperación corresponden íntegramente a StablR Ltd, entidad emisora de ambos tokens. La operativa en Bit2Me se reactivará en el momento en que StablR restablezca el servicio de forma segura.
Mantendremos esta página actualizada conforme el emisor publique nueva información oficial.
Gracias por tu paciencia y comprensión.
(Comunicado oficial de StablR: stablr.com/insights/further-update-concerning-the-cybersecurity-incident-affecting-eurr-usdr / Contacto: info@stablr.com)
--------
We share the latest official update issued by StablR Ltd. regarding the cybersecurity incident detected on May 24th. The issuer reports that it continues to execute its Recovery Plan in collaboration with the Malta Financial Services Authority (MFSA), with the company's priority being: the protection of token holders, the integrity of the recovery process, and the orderly assessment of the situation to determine the next steps.
Key points:
- Suspended operations: The minting, redemption, deposits, and withdrawals of EURR and USDR remain temporarily suspended across all platforms until further notice.
- Secure reserves: StablR reiterates that the reserve assets backing both tokens remain fully segregated and protected.
- Security alert: Users are reminded to rely solely on official channels. The issuer will never request private keys, passwords, or payments.
Bit2Me Note
The management of this incident and the execution of the recovery plan correspond entirely to StablR Ltd, the issuing entity of both tokens. Operations on Bit2Me will be reactivated as soon as StablR safely restores the service.
We will keep this page updated as the issuer publishes new official information.
Thank you for your patience and understanding.
(Official statement from StablR: stablr.com/insights/further-update-concerning-the-cybersecurity-incident-affecting-eurr-usdr / Contact: info@stablr.com)
Jun 05, 2026 - 12:39 CEST
Puntos clave:
- Operativa suspendida: La emisión, canje, depósitos y retiradas de EURR y USDR se mantienen temporalmente suspendidos en todas las plataformas hasta nuevo aviso.
- Reservas seguras: StablR reitera que los activos de reserva que respaldan ambos tokens siguen estando completamente segregados y protegidos.
- Alerta de seguridad: Se recuerda a los usuarios confiar únicamente en canales oficiales. El emisor nunca solicitará claves privadas, contraseñas ni pagos.
Nota de Bit2Me
La gestión de este incidente y la ejecución del plan de recuperación corresponden íntegramente a StablR Ltd, entidad emisora de ambos tokens. La operativa en Bit2Me se reactivará en el momento en que StablR restablezca el servicio de forma segura.
Mantendremos esta página actualizada conforme el emisor publique nueva información oficial.
Gracias por tu paciencia y comprensión.
(Comunicado oficial de StablR: stablr.com/insights/further-update-concerning-the-cybersecurity-incident-affecting-eurr-usdr / Contacto: info@stablr.com)
--------
We share the latest official update issued by StablR Ltd. regarding the cybersecurity incident detected on May 24th. The issuer reports that it continues to execute its Recovery Plan in collaboration with the Malta Financial Services Authority (MFSA), with the company's priority being: the protection of token holders, the integrity of the recovery process, and the orderly assessment of the situation to determine the next steps.
Key points:
- Suspended operations: The minting, redemption, deposits, and withdrawals of EURR and USDR remain temporarily suspended across all platforms until further notice.
- Secure reserves: StablR reiterates that the reserve assets backing both tokens remain fully segregated and protected.
- Security alert: Users are reminded to rely solely on official channels. The issuer will never request private keys, passwords, or payments.
Bit2Me Note
The management of this incident and the execution of the recovery plan correspond entirely to StablR Ltd, the issuing entity of both tokens. Operations on Bit2Me will be reactivated as soon as StablR safely restores the service.
We will keep this page updated as the issuer publishes new official information.
Thank you for your patience and understanding.
(Official statement from StablR: stablr.com/insights/further-update-concerning-the-cybersecurity-incident-affecting-eurr-usdr / Contact: info@stablr.com)
Jun 05, 2026 - 12:39 CEST
Update - En relación con la suspensión temporal de la operativa de EURR y USDR comunicada el pasado 25 de mayo, compartimos la última actualización oficial emitida por el emisor de estos activos, StablR Ltd.
StablR ha comunicado la activación formal de su Plan de Recuperación tras el incidente de ciberseguridad detectado el 24 de mayo, en coordinación con la Malta Financial Services Authority (MFSA) y bajo el marco regulatorio MiCAR.
Puntos clave del comunicado de StablR:
- Operativa suspendida. Las actividades de emisión, canje, depósitos y retiradas de EURR y USDR permanecen temporalmente suspendidas por orden del emisor en todas las plataformas.
- Fondos respaldados e intactos. StablR indica que todos los activos de reserva que respaldan ambos tokens se encuentran en cuentas segregadas y fondos monetarios independientes. Según los análisis actuales del emisor, el incidente no ha afectado a las reservas.
- Investigación en curso. Especialistas externos en ciberseguridad continúan trabajando para determinar el alcance completo del incidente en la infraestructura de StablR.
Nota de Bit2Me
La gestión de este incidente y la ejecución del plan de recuperación corresponden íntegramente a StablR Ltd, entidad emisora de ambos tokens. La operativa en Bit2Me se reactivará en el momento en que StablR restablezca el servicio de forma segura.
Mantendremos esta página actualizada conforme el emisor publique nueva información oficial.
Gracias por tu paciencia y comprensión.
(Comunicado oficial de StablR: stablr.com/insights/stablr-discloses-cybersecurity-incident-affecting-usdr-and-eurr-token-operations )
--------
In relation to the temporary suspension of EURR and USDR operations announced on May 25th, we are sharing the latest official update issued by the asset creator, StablR Ltd.
StablR has announced the formal activation of its Recovery Plan following the cybersecurity incident detected on May 24th, in coordination with the Malta Financial Services Authority (MFSA) and under the MiCAR regulatory framework.
Key points from StablR's statement:
- Operations suspended. Minting, redemption, deposit, and withdrawal activities for EURR and USDR remain temporarily suspended across all platforms by order of the issuer.
- Funds backed and intact. StablR indicates that all reserve assets backing both tokens are held in segregated accounts and independent money market funds. According to the issuer's current analysis, the incident has not affected these reserves.
- Ongoing investigation. External cybersecurity specialists continue to work on determining the full scope of the incident within StablR's infrastructure.
Note from Bit2Me
The management of this incident and the execution of the recovery plan are entirely the responsibility of StablR Ltd, the issuing entity of both tokens. Operations on Bit2Me will resume as soon as StablR safely restores its service.
We will keep this page updated as the issuer releases new official information.
Thank you for your patience and understanding.
(Official statement from StablR: stablr.com/insights/stablr-discloses-cybersecurity-incident-affecting-usdr-and-eurr-token-operations )
Jun 03, 2026 - 12:37 CEST
StablR ha comunicado la activación formal de su Plan de Recuperación tras el incidente de ciberseguridad detectado el 24 de mayo, en coordinación con la Malta Financial Services Authority (MFSA) y bajo el marco regulatorio MiCAR.
Puntos clave del comunicado de StablR:
- Operativa suspendida. Las actividades de emisión, canje, depósitos y retiradas de EURR y USDR permanecen temporalmente suspendidas por orden del emisor en todas las plataformas.
- Fondos respaldados e intactos. StablR indica que todos los activos de reserva que respaldan ambos tokens se encuentran en cuentas segregadas y fondos monetarios independientes. Según los análisis actuales del emisor, el incidente no ha afectado a las reservas.
- Investigación en curso. Especialistas externos en ciberseguridad continúan trabajando para determinar el alcance completo del incidente en la infraestructura de StablR.
Nota de Bit2Me
La gestión de este incidente y la ejecución del plan de recuperación corresponden íntegramente a StablR Ltd, entidad emisora de ambos tokens. La operativa en Bit2Me se reactivará en el momento en que StablR restablezca el servicio de forma segura.
Mantendremos esta página actualizada conforme el emisor publique nueva información oficial.
Gracias por tu paciencia y comprensión.
(Comunicado oficial de StablR: stablr.com/insights/stablr-discloses-cybersecurity-incident-affecting-usdr-and-eurr-token-operations )
--------
In relation to the temporary suspension of EURR and USDR operations announced on May 25th, we are sharing the latest official update issued by the asset creator, StablR Ltd.
StablR has announced the formal activation of its Recovery Plan following the cybersecurity incident detected on May 24th, in coordination with the Malta Financial Services Authority (MFSA) and under the MiCAR regulatory framework.
Key points from StablR's statement:
- Operations suspended. Minting, redemption, deposit, and withdrawal activities for EURR and USDR remain temporarily suspended across all platforms by order of the issuer.
- Funds backed and intact. StablR indicates that all reserve assets backing both tokens are held in segregated accounts and independent money market funds. According to the issuer's current analysis, the incident has not affected these reserves.
- Ongoing investigation. External cybersecurity specialists continue to work on determining the full scope of the incident within StablR's infrastructure.
Note from Bit2Me
The management of this incident and the execution of the recovery plan are entirely the responsibility of StablR Ltd, the issuing entity of both tokens. Operations on Bit2Me will resume as soon as StablR safely restores its service.
We will keep this page updated as the issuer releases new official information.
Thank you for your patience and understanding.
(Official statement from StablR: stablr.com/insights/stablr-discloses-cybersecurity-incident-affecting-usdr-and-eurr-token-operations )
Jun 03, 2026 - 12:37 CEST
Monitoring - La operativa de EURR y USDR está temporalmente suspendida por un incidente externo en el proveedor del activo. Reactivaremos en cuanto confirmemos que la situación está resuelta.
--------
EURR and USDR operations are temporarily suspended due to an external incident with the asset provider. We will reactivate as soon as we confirm that the situation is resolved.
May 25, 2026 - 12:35 CEST
--------
EURR and USDR operations are temporarily suspended due to an external incident with the asset provider. We will reactivate as soon as we confirm that the situation is resolved.
May 25, 2026 - 12:35 CEST
Monitoring - - Inicio: lunes, 31 de agosto de 2026, 00:00h (CEST)
- Fin: lunes, 31 de agosto de 2026, 08:00h (CEST)
- Duración estimada: 8 horas
Durante el mantenimiento programado, todos los servicios de la Suite de Bit2Me podrían experimentar interrupciones.
Estas tareas de mantenimiento se realizan periódicamente con el objetivo de implementar mejoras y garantizar el buen funcionamiento del sistema. Lamentamos de antemano las molestias que esta interrupción pueda ocasionarles. Tan pronto finalicen las tareas de mantenimiento, se restablecerá la operativa con total normalidad.
--------
- Start: Monday, August 31st, 2026, 00:00h (CEST)
- End: Monday, August 31st, 2026, 08:00h (CEST)
- Estimated duration: 8 hours
During the scheduled maintenance, all services within the Bit2Me Suite may experience interruptions.
These maintenance tasks are carried out periodically with the aim of implementing improvements and ensuring the proper functioning of the system. We apologize in advance for any inconvenience this interruption may cause. As soon as the maintenance tasks are completed, operations will resume with total normality.
Aug 14, 2026 - 15:57 CEST
- Fin: lunes, 31 de agosto de 2026, 08:00h (CEST)
- Duración estimada: 8 horas
Durante el mantenimiento programado, todos los servicios de la Suite de Bit2Me podrían experimentar interrupciones.
Estas tareas de mantenimiento se realizan periódicamente con el objetivo de implementar mejoras y garantizar el buen funcionamiento del sistema. Lamentamos de antemano las molestias que esta interrupción pueda ocasionarles. Tan pronto finalicen las tareas de mantenimiento, se restablecerá la operativa con total normalidad.
--------
- Start: Monday, August 31st, 2026, 00:00h (CEST)
- End: Monday, August 31st, 2026, 08:00h (CEST)
- Estimated duration: 8 hours
During the scheduled maintenance, all services within the Bit2Me Suite may experience interruptions.
These maintenance tasks are carried out periodically with the aim of implementing improvements and ensuring the proper functioning of the system. We apologize in advance for any inconvenience this interruption may cause. As soon as the maintenance tasks are completed, operations will resume with total normality.
Aug 14, 2026 - 15:57 CEST
Actualización en el algoritmo de generación de la firma de la API / Update to the API signature generation algorithm.
Subscribe
Identified - Para mejorar la consistencia en la validación de nuestras solicitudes, vamos a introducir un cambio en la forma en que se generan las firmas de autenticación. Este cambio afecta exclusivamente a las peticiones que incluyen un cuerpo (body) vacío.
A partir del día 08/10/2026, las peticiones con un cuerpo vacío {} deberán incluir dicho contenido en la cadena de texto utilizada para generar la firma.
- Comportamiento actual (Deprecado): El cuerpo vacío se omite en la cadena de firma.
- Nuevo comportamiento (Requerido): El cuerpo vacío {} debe concatenarse al final de la cadena.
Ejemplos:
Para una petición a /v1/signin/apikey con un body {} y un timestamp 123123123:
Formato Actual (Legacy) 123123123:/v1/signin/apikey
Formato Nuevo (Requerido) 123123123:/v1/signin/apikey:{}
Nota: Las peticiones que no tienen body (ej. GET) o aquellas que tienen un body con datos no se ven afectadas y deben seguir generando la misma cadena de texto de firma.
--------
To improve consistency in the validation of our requests, we are introducing a change in how authentication signatures are generated. This change exclusively affects requests that include an empty body.
Starting 10/08/2026, requests with an empty body {} must include that content in the string used to generate the signature.
- Current Behavior (Deprecated): The empty body is omitted from the signature string.New
- Behavior (Required): The empty body {} must be concatenated at the end of the string.
Examples:
For a request to /v1/signin/apikey with a body {} and a timestamp 123123123:
Current Format (Legacy): 123123123:/v1/signin/apikey
New Format (Required): 123123123:/v1/signin/apikey:{}
Apr 08, 2026 - 08:37 CEST
A partir del día 08/10/2026, las peticiones con un cuerpo vacío {} deberán incluir dicho contenido en la cadena de texto utilizada para generar la firma.
- Comportamiento actual (Deprecado): El cuerpo vacío se omite en la cadena de firma.
- Nuevo comportamiento (Requerido): El cuerpo vacío {} debe concatenarse al final de la cadena.
Ejemplos:
Para una petición a /v1/signin/apikey con un body {} y un timestamp 123123123:
Formato Actual (Legacy) 123123123:/v1/signin/apikey
Formato Nuevo (Requerido) 123123123:/v1/signin/apikey:{}
Nota: Las peticiones que no tienen body (ej. GET) o aquellas que tienen un body con datos no se ven afectadas y deben seguir generando la misma cadena de texto de firma.
--------
To improve consistency in the validation of our requests, we are introducing a change in how authentication signatures are generated. This change exclusively affects requests that include an empty body.
Starting 10/08/2026, requests with an empty body {} must include that content in the string used to generate the signature.
- Current Behavior (Deprecated): The empty body is omitted from the signature string.New
- Behavior (Required): The empty body {} must be concatenated at the end of the string.
Examples:
For a request to /v1/signin/apikey with a body {} and a timestamp 123123123:
Current Format (Legacy): 123123123:/v1/signin/apikey
New Format (Required): 123123123:/v1/signin/apikey:{}
Apr 08, 2026 - 08:37 CEST
Incidencia en la red Ravencoin (RVN): operativa suspendida temporalmente / Incident in the Ravencoin network (RVN): operations temporarily suspended
Subscribe
Monitoring - Hemos suspendido de forma temporal y preventiva la operativa con Ravencoin (RVN) en Bit2Me.
--> Qué ocurre.
El 10 de agosto de 2026, Ravencoin publicó un aviso oficial en el que comunica que se ha explotado una vulnerabilidad crítica en el mecanismo de consenso de su red, que provocó la aceptación de bloques inválidos por parte de nodos vulnerables. Según ese aviso, el primer bloque inválido conocido se produjo en la altura 4.487.776 el 7 de agosto de 2026, y los pools que concentran la mayoría del hash rate de la red están minando una cadena que excluye la rama explotada desde ese punto. El propio aviso indica que, si esa cadena pasa a ser la dominante, podría producirse una reorganización profunda de la cadena de aproximadamente tres días, y recomienda a las plataformas de intercambio suspender temporalmente los depósitos y retiros de RVN hasta que el estado de la red sea estable.
Esta incidencia se produce en la red Ravencoin. No afecta a la infraestructura ni a los sistemas de Bit2Me.
--> Estado de la operativa con RVN.
- Compra, venta y swap: suspendidos desde la tarde del 12 de agosto de 2026 (hora peninsular española)
- Retiro de RVN a wallets externas: suspendido desde la tarde del 12 de agosto de 2026 (hora peninsular española)
- Depósito de RVN desde wallets externas: suspendido
--> Tu saldo.
Tu saldo de RVN permanece registrado íntegro en tu cuenta de Bit2Me. Mientras la suspensión esté activa no es posible operar con él ni retirarlo.
---> Por qué hemos tomado esta medida.
Para evitar que operaciones realizadas durante el proceso de reorganización de la red queden revertidas.
--> Resto de servicios
El resto de criptoactivos y servicios de Bit2Me operan con normalidad.
--> Qué debes hacer
No es necesaria ninguna acción por tu parte.
--> Próxima actualización
Seguimos la evolución de la red y actualizaremos la información mediante este mismo comunicado.
Restableceremos la operativa con RVN cuando el estado de la cadena sea estable y nuestras verificaciones internas lo confirmen.
--------
We have temporarily and preventively suspended operations involving Ravencoin (RVN) on Bit2Me.
--> What is happening.
On August 10, 2026, Ravencoin published an official notice reporting that a critical vulnerability in its network's consensus mechanism had been exploited, causing vulnerable nodes to accept invalid blocks. According to that notice, the first known invalid block occurred at block height 4,487,776 on August 7, 2026, and the pools that account for the majority of the network's hash rate are mining a chain that excludes the exploited branch from that point onward. The notice itself states that, if this chain becomes the dominant one, a deep chain reorganization of roughly three days could occur, and it recommends that exchanges temporarily suspend RVN deposits and withdrawals until the network's status is stable.
This incident is occurring on the Ravencoin network. It does not affect Bit2Me's infrastructure or systems.
--> Status of RVN operations.
- Buying, selling, and swapping: suspended since the afternoon of August 12, 2026 (Spanish mainland time)
- RVN withdrawals to external wallets: suspended since the afternoon of August 12, 2026 (Spanish mainland time)
- RVN deposits from external wallets: suspended
--> Your balance.
Your RVN balance remains fully intact in your Bit2Me account. While the suspension is in effect, it cannot be traded or withdrawn.
--> Why we have taken this measure.
To prevent transactions carried out during the network's reorganization process from being reverted.
--> Other services
All other Bit2Me crypto assets and services are operating normally.
--> What you need to do
No action is required on your part.
--> Next update
We are monitoring the network's progress and will update this information through this same notice.
We will restore RVN operations once the chain's status is stable and our internal checks confirm it.
Aug 12, 2026 - 15:25 CEST
--> Qué ocurre.
El 10 de agosto de 2026, Ravencoin publicó un aviso oficial en el que comunica que se ha explotado una vulnerabilidad crítica en el mecanismo de consenso de su red, que provocó la aceptación de bloques inválidos por parte de nodos vulnerables. Según ese aviso, el primer bloque inválido conocido se produjo en la altura 4.487.776 el 7 de agosto de 2026, y los pools que concentran la mayoría del hash rate de la red están minando una cadena que excluye la rama explotada desde ese punto. El propio aviso indica que, si esa cadena pasa a ser la dominante, podría producirse una reorganización profunda de la cadena de aproximadamente tres días, y recomienda a las plataformas de intercambio suspender temporalmente los depósitos y retiros de RVN hasta que el estado de la red sea estable.
Esta incidencia se produce en la red Ravencoin. No afecta a la infraestructura ni a los sistemas de Bit2Me.
--> Estado de la operativa con RVN.
- Compra, venta y swap: suspendidos desde la tarde del 12 de agosto de 2026 (hora peninsular española)
- Retiro de RVN a wallets externas: suspendido desde la tarde del 12 de agosto de 2026 (hora peninsular española)
- Depósito de RVN desde wallets externas: suspendido
--> Tu saldo.
Tu saldo de RVN permanece registrado íntegro en tu cuenta de Bit2Me. Mientras la suspensión esté activa no es posible operar con él ni retirarlo.
---> Por qué hemos tomado esta medida.
Para evitar que operaciones realizadas durante el proceso de reorganización de la red queden revertidas.
--> Resto de servicios
El resto de criptoactivos y servicios de Bit2Me operan con normalidad.
--> Qué debes hacer
No es necesaria ninguna acción por tu parte.
--> Próxima actualización
Seguimos la evolución de la red y actualizaremos la información mediante este mismo comunicado.
Restableceremos la operativa con RVN cuando el estado de la cadena sea estable y nuestras verificaciones internas lo confirmen.
--------
We have temporarily and preventively suspended operations involving Ravencoin (RVN) on Bit2Me.
--> What is happening.
On August 10, 2026, Ravencoin published an official notice reporting that a critical vulnerability in its network's consensus mechanism had been exploited, causing vulnerable nodes to accept invalid blocks. According to that notice, the first known invalid block occurred at block height 4,487,776 on August 7, 2026, and the pools that account for the majority of the network's hash rate are mining a chain that excludes the exploited branch from that point onward. The notice itself states that, if this chain becomes the dominant one, a deep chain reorganization of roughly three days could occur, and it recommends that exchanges temporarily suspend RVN deposits and withdrawals until the network's status is stable.
This incident is occurring on the Ravencoin network. It does not affect Bit2Me's infrastructure or systems.
--> Status of RVN operations.
- Buying, selling, and swapping: suspended since the afternoon of August 12, 2026 (Spanish mainland time)
- RVN withdrawals to external wallets: suspended since the afternoon of August 12, 2026 (Spanish mainland time)
- RVN deposits from external wallets: suspended
--> Your balance.
Your RVN balance remains fully intact in your Bit2Me account. While the suspension is in effect, it cannot be traded or withdrawn.
--> Why we have taken this measure.
To prevent transactions carried out during the network's reorganization process from being reverted.
--> Other services
All other Bit2Me crypto assets and services are operating normally.
--> What you need to do
No action is required on your part.
--> Next update
We are monitoring the network's progress and will update this information through this same notice.
We will restore RVN operations once the chain's status is stable and our internal checks confirm it.
Aug 12, 2026 - 15:25 CEST
Cambio programado: precisión decimal en Bit2Me Pro Trading Spot API / Scheduled Change: Decimal Precision in Bit2Me Pro Trading Spot API
Subscribe
Monitoring - A partir del 10 de febrero de 2027, la precisión decimal de determinados campos numéricos de trading en la API de Bit2Me Pro Trading Spot pasará a admitir hasta un máximo de 18 decimales.
Alcance:
- API documentada en: https://api.bit2me.com/doc#tag/pro-trading-spot
Campos afectados:
- Trades
- price
- amount
- cost
- costEuro
- feeAmount
- Orders
- orderAmount
- filledAmount
- dustAmount
- cost
- feeAmount
- balance
- blockedBalance
Acción recomendada para integradores:
Revisar el tratamiento de valores numéricos en sus sistemas (parsing, redondeo, almacenamiento y conciliación) para garantizar la correcta gestión de hasta 18 decimales en los campos indicados.
Este anuncio se publica con antelación para facilitar la adaptación técnica. Para cualquier duda, contacte con su interlocutor habitual de Bit2Me API / soporte.
--------
Effective 10 February 2027, the decimal precision of certain numeric trading fields in the Bit2Me Pro Trading Spot API will support up to a maximum of 18 decimal places.
Scope:
- API documentation: https://api.bit2me.com/doc#tag/pro-trading-spot
Affected fields:
- Trades
- price
- amount
- cost
- costEuro
- feeAmount
- Orders
- orderAmount
- filledAmount
- dustAmount
- cost
- feeAmount
- balance
- blockedBalance
Recommended action for integrators:
Please review how numeric values are handled in your systems (parsing, rounding, storage and reconciliation) to ensure correct support for up to 18 decimal places in the fields listed above.
This notice is published in advance to allow sufficient time for technical adaptation. For any questions, please contact your usual Bit2Me API counterpart / support channel.
Aug 12, 2026 - 12:29 CEST
Alcance:
- API documentada en: https://api.bit2me.com/doc#tag/pro-trading-spot
Campos afectados:
- Trades
- price
- amount
- cost
- costEuro
- feeAmount
- Orders
- orderAmount
- filledAmount
- dustAmount
- cost
- feeAmount
- balance
- blockedBalance
Acción recomendada para integradores:
Revisar el tratamiento de valores numéricos en sus sistemas (parsing, redondeo, almacenamiento y conciliación) para garantizar la correcta gestión de hasta 18 decimales en los campos indicados.
Este anuncio se publica con antelación para facilitar la adaptación técnica. Para cualquier duda, contacte con su interlocutor habitual de Bit2Me API / soporte.
--------
Effective 10 February 2027, the decimal precision of certain numeric trading fields in the Bit2Me Pro Trading Spot API will support up to a maximum of 18 decimal places.
Scope:
- API documentation: https://api.bit2me.com/doc#tag/pro-trading-spot
Affected fields:
- Trades
- price
- amount
- cost
- costEuro
- feeAmount
- Orders
- orderAmount
- filledAmount
- dustAmount
- cost
- feeAmount
- balance
- blockedBalance
Recommended action for integrators:
Please review how numeric values are handled in your systems (parsing, rounding, storage and reconciliation) to ensure correct support for up to 18 decimal places in the fields listed above.
This notice is published in advance to allow sufficient time for technical adaptation. For any questions, please contact your usual Bit2Me API counterpart / support channel.
Aug 12, 2026 - 12:29 CEST
Monitoring - We are carrying out maintenance work on the PIX payment method. For this reason, purchases via PIX will remain temporarily disabled. As soon as the maintenance is completed, they will be reactivated automatically. The current status of the operations associated with this payment method is as follows:
- Purchases with PIX: Temporarily disabled
- Deposits with PIX: Enabled
- Withdrawals: Enabled
If you wish to buy a cryptocurrency, you can make a deposit via PIX and, once you receive the funds, complete the purchase using the euro balance available in your Bit2Me account. → https://support.bit2me.com/en/support/solutions/articles/35000298414
For any questions, contact our support team.
--------
Estamos realizando tarefas de manutenção no método de pagamento PIX. Por esse motivo, as compras via PIX permanecerão temporariamente desativadas. Assim que a manutenção for concluída, elas serão reativadas automaticamente. O status atual das operações associadas a este método de pagamento é o seguinte:
- Compras com PIX: Temporariamente desativadas
- Depósitos com PIX: Ativados
- Saques: Ativados
Se você deseja comprar uma criptomoeda, pode realizar um depósito via PIX e, assim que receber os fundos, efetuar a compra com o saldo em euros disponível na sua conta Bit2Me. → https://support.bit2me.com/pt-BR/support/solutions/articles/35000298414
Em caso de dúvida, entre em contato com nossa equipe de suporte.
Jul 21, 2026 - 10:28 CEST
- Purchases with PIX: Temporarily disabled
- Deposits with PIX: Enabled
- Withdrawals: Enabled
If you wish to buy a cryptocurrency, you can make a deposit via PIX and, once you receive the funds, complete the purchase using the euro balance available in your Bit2Me account. → https://support.bit2me.com/en/support/solutions/articles/35000298414
For any questions, contact our support team.
--------
Estamos realizando tarefas de manutenção no método de pagamento PIX. Por esse motivo, as compras via PIX permanecerão temporariamente desativadas. Assim que a manutenção for concluída, elas serão reativadas automaticamente. O status atual das operações associadas a este método de pagamento é o seguinte:
- Compras com PIX: Temporariamente desativadas
- Depósitos com PIX: Ativados
- Saques: Ativados
Se você deseja comprar uma criptomoeda, pode realizar um depósito via PIX e, assim que receber os fundos, efetuar a compra com o saldo em euros disponível na sua conta Bit2Me. → https://support.bit2me.com/pt-BR/support/solutions/articles/35000298414
Em caso de dúvida, entre em contato com nossa equipe de suporte.
Jul 21, 2026 - 10:28 CEST
Monitoring - Duration: 6 months
Bit2Me will be deprecating the following endpoints on January 11, 2027. This change will affect users currently using the deprecated endpoints.
POST /v1/account/address
GET /v2/account/address
POST /v1/account/reset/password
PUT /v1/account/reset/password
PUT /v1/account/verify/phone
GET /v1/account/professions
GET /v1/account/purposes
GET /v1/account/employment-status
GET /v1/account/funds-origin
GET /v1/account/politically-exposed
GET /v1/account/identity-type/all
PUT /v2/account/reset/password
POST /v2/account/sfa/call
GET /v1/card/cards/{cardId}/balance
PATCH /v1/card/cards/{cardId}/activate
POST /v1/card/payments/proforma
POST /v1/card/payments/{paymentId}/proforma
PATCH /v2/card/cards/{cardId}
GET /v1/type
GET /v1/currency/convert
GET /v1/notification/feed
GET /v1/trading/market-config
GET /v1/trading/market-config/{base}/{quote}
GET /v1/taxes/report/file/{year}
POST /v2/account/verify/identity/verification-id
GET /v2/wallet/transaction
GET /v1/5d5b377275a9bfa1/balances/current
GET /v1/5d5b377275a9bfa1/jwks
POST /v1/5d5b377275a9bfa1/notification/send
POST /v1/5d5b377275a9bfa1/document-notification
POST /v1/5d5b377275a9bfa1/orders/lock-balance
POST /v1/5d5b377275a9bfa1/orders/purchase-success
POST /v1/5d5b377275a9bfa1/orders/purchase-failed
POST /v1/5d5b377275a9bfa1/orders/payouts
POST /v1/5d5b377275a9bfa1/orders/dividend/reward
GET /v2/signin/sfa
GET /v1/card/cards/{cardId}
DELETE /v1/card/cards/{cardId}
GET /v1/card/customers/{customerId}/update_secret_code
POST /v1/card/customers/{customerId}/update_secret_code
PATCH /v1/card/customers/{customerId}/update_phone_number
POST /v1/card/customers/{customerId}/update_phone_number
GET /v1/verifier/identity-type/all
POST /v2/account/verify/identity/init
Please find the new version of the previous endpoints on the official Bit2Me API website. Below, we provide a direct link for each endpoint:
POST /v2/account/address: B2M API
GET /v3/account/address: B2M API
POST /v2/account/reset/password: B2M API
PUT /v2/account/reset/password: B2M API
PUT /v1/verifier/verify/phone: B2M API
GET /v2/account/professions: B2M API
GET /v2/account/purposes: B2M API
GET /v2/account/employment-status: B2M API
GET /v2/account/funds-origin: B2M API
GET /v2/account/politically-exposed: B2M API
GET /v1/verifier/identity-type/all: B2M API
PUT /v3/account/reset/password: B2M API
POST /v3/account/sfa/call: B2M API
GET /v2/card/cards/{cardId}/balance: B2M API
PATCH /v2/card/cards/{cardId}/activate: B2M API
POST /v2/card/payments/proforma: B2M API
POST /v2/card/payments/{paymentId}/proforma: B2M API
PATCH /v4/card/cards/{cardId}: B2M API
GET /v1/currency/catalog?type=fiat: B2M API
GET /v1/currency/prices o GET /v1/currency/rate: B2M API
GET /v2/notification/feed: B2M API
GET /v2/trading/market-config: B2M API
GET /v2/trading/market-config/{base}/{quote}: B2M API
GET /v2/taxes/report/file/{year}: B2M API
POST /v2/verifier/identity-verification/callback: B2M API
GET /v3/wallet/transaction: B2M API
GET /v1/stocks/5d5b377275a9bfa1/balances/current
GET /v1/stocks/5d5b377275a9bfa1/jwks
POST /v1/stocks/5d5b377275a9bfa1/notification/send
POST /v1/stocks/5d5b377275a9bfa1/document-notification
POST /v1/stocks/5d5b377275a9bfa1/orders/lock-balance
POST /v1/stocks/5d5b377275a9bfa1/orders/purchase-success
POST /v1/stocks/5d5b377275a9bfa1/orders/purchase-failed
POST /v1/stocks/5d5b377275a9bfa1/orders/payouts
POST /v1/stocks/5d5b377275a9bfa1/orders/dividend/reward
🔄 Steps to Update Your Integration:
Review the list of deprecated endpoints and their updated alternatives before January 11, 2027.
Once your integration is updated, you're all set!
If you have any questions or need assistance, feel free to open a support ticket or contact our support team.
Jul 09, 2026 - 16:20 CEST
Bit2Me will be deprecating the following endpoints on January 11, 2027. This change will affect users currently using the deprecated endpoints.
POST /v1/account/address
GET /v2/account/address
POST /v1/account/reset/password
PUT /v1/account/reset/password
PUT /v1/account/verify/phone
GET /v1/account/professions
GET /v1/account/purposes
GET /v1/account/employment-status
GET /v1/account/funds-origin
GET /v1/account/politically-exposed
GET /v1/account/identity-type/all
PUT /v2/account/reset/password
POST /v2/account/sfa/call
GET /v1/card/cards/{cardId}/balance
PATCH /v1/card/cards/{cardId}/activate
POST /v1/card/payments/proforma
POST /v1/card/payments/{paymentId}/proforma
PATCH /v2/card/cards/{cardId}
GET /v1/type
GET /v1/currency/convert
GET /v1/notification/feed
GET /v1/trading/market-config
GET /v1/trading/market-config/{base}/{quote}
GET /v1/taxes/report/file/{year}
POST /v2/account/verify/identity/verification-id
GET /v2/wallet/transaction
GET /v1/5d5b377275a9bfa1/balances/current
GET /v1/5d5b377275a9bfa1/jwks
POST /v1/5d5b377275a9bfa1/notification/send
POST /v1/5d5b377275a9bfa1/document-notification
POST /v1/5d5b377275a9bfa1/orders/lock-balance
POST /v1/5d5b377275a9bfa1/orders/purchase-success
POST /v1/5d5b377275a9bfa1/orders/purchase-failed
POST /v1/5d5b377275a9bfa1/orders/payouts
POST /v1/5d5b377275a9bfa1/orders/dividend/reward
GET /v2/signin/sfa
GET /v1/card/cards/{cardId}
DELETE /v1/card/cards/{cardId}
GET /v1/card/customers/{customerId}/update_secret_code
POST /v1/card/customers/{customerId}/update_secret_code
PATCH /v1/card/customers/{customerId}/update_phone_number
POST /v1/card/customers/{customerId}/update_phone_number
GET /v1/verifier/identity-type/all
POST /v2/account/verify/identity/init
Please find the new version of the previous endpoints on the official Bit2Me API website. Below, we provide a direct link for each endpoint:
POST /v2/account/address: B2M API
GET /v3/account/address: B2M API
POST /v2/account/reset/password: B2M API
PUT /v2/account/reset/password: B2M API
PUT /v1/verifier/verify/phone: B2M API
GET /v2/account/professions: B2M API
GET /v2/account/purposes: B2M API
GET /v2/account/employment-status: B2M API
GET /v2/account/funds-origin: B2M API
GET /v2/account/politically-exposed: B2M API
GET /v1/verifier/identity-type/all: B2M API
PUT /v3/account/reset/password: B2M API
POST /v3/account/sfa/call: B2M API
GET /v2/card/cards/{cardId}/balance: B2M API
PATCH /v2/card/cards/{cardId}/activate: B2M API
POST /v2/card/payments/proforma: B2M API
POST /v2/card/payments/{paymentId}/proforma: B2M API
PATCH /v4/card/cards/{cardId}: B2M API
GET /v1/currency/catalog?type=fiat: B2M API
GET /v1/currency/prices o GET /v1/currency/rate: B2M API
GET /v2/notification/feed: B2M API
GET /v2/trading/market-config: B2M API
GET /v2/trading/market-config/{base}/{quote}: B2M API
GET /v2/taxes/report/file/{year}: B2M API
POST /v2/verifier/identity-verification/callback: B2M API
GET /v3/wallet/transaction: B2M API
GET /v1/stocks/5d5b377275a9bfa1/balances/current
GET /v1/stocks/5d5b377275a9bfa1/jwks
POST /v1/stocks/5d5b377275a9bfa1/notification/send
POST /v1/stocks/5d5b377275a9bfa1/document-notification
POST /v1/stocks/5d5b377275a9bfa1/orders/lock-balance
POST /v1/stocks/5d5b377275a9bfa1/orders/purchase-success
POST /v1/stocks/5d5b377275a9bfa1/orders/purchase-failed
POST /v1/stocks/5d5b377275a9bfa1/orders/payouts
POST /v1/stocks/5d5b377275a9bfa1/orders/dividend/reward
🔄 Steps to Update Your Integration:
Review the list of deprecated endpoints and their updated alternatives before January 11, 2027.
Once your integration is updated, you're all set!
If you have any questions or need assistance, feel free to open a support ticket or contact our support team.
Jul 09, 2026 - 16:20 CEST
Monitoring - La operativa de las siguientes monedas se encuentra detenida de forma temporal: GODS, AZERO, RIO y BDX.
En estos momentos, nuestro equipo está revisando la situación para restablecer el servicio lo antes posible.
Os mantendremos informados a través de este canal ante cualquier novedad.
--------
Trading for the following currencies is temporarily suspended: GODS, AZERO, RIO, and BDX.
At this time, our team is reviewing the situation to restore service as soon as possible. We will keep you informed through this channel of any updates.
May 15, 2026 - 12:41 CEST
En estos momentos, nuestro equipo está revisando la situación para restablecer el servicio lo antes posible.
Os mantendremos informados a través de este canal ante cualquier novedad.
--------
Trading for the following currencies is temporarily suspended: GODS, AZERO, RIO, and BDX.
At this time, our team is reviewing the situation to restore service as soon as possible. We will keep you informed through this channel of any updates.
May 15, 2026 - 12:41 CEST
Identified - Bit2Me will be deprecating the following endpoint on September 28, 2026. This change will affect users currently using this deprecated route.
GET /v1/type
-----
🔄 Steps to Update Your Integration:
Review the use of the deprecated endpoint and migrate to the updated alternative before September 28, 2026.
Once your integration is updated, you’re all set!
If you have any questions or need assistance, feel free to open a support ticket or contact our support team.
Apr 08, 2026 - 08:36 CEST
GET /v1/type
-----
🔄 Steps to Update Your Integration:
Review the use of the deprecated endpoint and migrate to the updated alternative before September 28, 2026.
Once your integration is updated, you’re all set!
If you have any questions or need assistance, feel free to open a support ticket or contact our support team.
Apr 08, 2026 - 08:36 CEST
Identified - Bit2Me will be deprecating the following endpoint on September 7, 2026. This change will affect users currently using this deprecated route.
Deprecated Endpoint:
GET /v1/currency/convert: https://api.bit2me.com/#tag/Currency/operation/convert
-----
🔄 Steps to Update Your Integration:
Review the use of the deprecated endpoint and migrate to the updated alternative before September 7, 2026.
Once your integration is updated, you’re all set!
If you have any questions or need assistance, feel free to open a support ticket or contact our support team.
Apr 08, 2026 - 08:38 CEST
Deprecated Endpoint:
GET /v1/currency/convert: https://api.bit2me.com/#tag/Currency/operation/convert
-----
🔄 Steps to Update Your Integration:
Review the use of the deprecated endpoint and migrate to the updated alternative before September 7, 2026.
Once your integration is updated, you’re all set!
If you have any questions or need assistance, feel free to open a support ticket or contact our support team.
Apr 08, 2026 - 08:38 CEST
About This Site
Your easiest and most complete cryptocurrency app in the world.
Services
Operational
Public Website
Operational
Auth
Operational
Wallet
Operational
Pro
Operational
Earn
Operational
Loan
Operational
Pay
Operational
Card
Operational
Tax
Operational
Launchpad
Operational
Life
Operational
Space Center
Operational
Simple Buy / Sell / Swap
Operational
API
Operational
Mobile APP
Operational
Android
Operational
iOS
Operational
Notifications
Operational
E-Mails
Operational
2FA SMS
Operational
Push
Operational
Other
Operational
Blog
Operational
Careers
Operational
Academy
Operational
News
Operational
Web3MBA
Operational
Support
Operational
Knowlege Base
Operational
Phone
Operational
Whatsapp
Operational
Tickets
Operational
Payment Methods (Cash - In / Cash - out)
Degraded Performance
Credit / Debit Card
Operational
SEPA Bank Transfer
Operational
Apple Pay
Operational
Google Pay
Operational
PIX Brazil
Degraded Performance
CVU Argentina
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
