# Mercury (ميركوري)

> Mercury is currently blocked in Syria, as of 2026-08-30.

- Status: blocked
- Outreach: Contacted
- Company: [Mercury Technologies](https://unblocksyria.com/en/companies/mercury-technologies.md)
- Categories: Digital Banks & Neobanks, Investment, Money Transfer, Payment Services
- Official site: https://mercury.com
- Community votes: 26
- Last updated: 2026-08-30
- Page: https://unblocksyria.com/en/services/mercury

## About

Digital banking platform for startups offering business accounts, payments, and treasury management

## Activity summary

Blocked in Syria, and declined three times in early 2026 with Mercury calling the decision final. A fresh request in August 2026 went further: Mercury Legal forwarded it to the company's Risk team rather than restating the refusal, and a follow-up to its compliance team is unanswered.

## Community reports

- 2026-08-29 — Follow-up Sent. The volunteer wrote again two days later, this time to Mercury's compliance team at compliance@mercury.com, and separately replied to Mercury's support team to restate the request as a country-policy review rather than an account matter. The reply acknowledged Mercury's position that the current restriction is shaped by its own risk assessments and banking-partner policies as well as by regulatory requirements, and asked Mercury to keep the matter formally recorded as a country-policy review request and to consider removing Syria from its blanket prohibited-country list once those assessments allow. It repeated that the request is not to weaken anti-money-laundering, know-your-customer or sanctions-screening controls, but to reassess whether a blanket country restriction is still the right instrument when individual parties can be screened.
- 2026-08-27 — Company Responded. Mercury's legal team replied five hours later confirming that the request had been forwarded to Mercury's Risk team, and that a member of that team would follow up directly if further information or action were required. The reply is brief and states no position and no timeline, but it is the first time Mercury has routed a Syria country-policy request onward instead of restating a refusal. Mercury had declined three times in February and March 2026, describing the decision as final, so this is a change in handling even though it is not yet a change in policy.
- 2026-08-27 — Company Responded. Mercury replied six minutes later with a message that identifies itself in its own text as Mercury's AI-powered support assistant. It did not address the policy question at all. Instead it said no account or application could be found for the address the message came from, and asked the sender either to log in to an existing account, to write from the address on file, or to reply with more detail. The reply is an automated identity-verification deflection rather than any engagement with the country-eligibility request, and it misses the point the sender had made explicitly: there is no account to log in to, because the country restriction is what prevents one being opened.
- 2026-08-27 — Follow-up Sent. A community volunteer emailed Mercury's support and legal teams at help@mercury.com and legal@mercury.com requesting a senior-level compliance and policy review of Mercury's classification of Syria as a prohibited country. The email set out that the United States rescinded Syria's designation as a state sponsor of terrorism on 24 August 2026, that Syria is no longer subject to the Terrorism List Governments Sanctions Regulations at 31 CFR Part 596, and that the comprehensive Syria sanctions programme was terminated by Executive Order 14312 effective 1 July 2025, leaving only targeted list-based measures. It asked Mercury to distinguish between a jurisdiction under comprehensive sanctions and specific parties under targeted sanctions, and to state plainly whether its Syria restriction rests on a legal requirement, an internal policy, banking-partner requirements, risk appetite, or a combination. Mercury had declined three times in February and March 2026, describing that decision as final.
- 2026-03-03 — Declined. Mercury's compliance team confirmed via compliance@mercury.com that Syria remains on Mercury's Prohibited Countries list and that the company cannot provide services to users in Syria — the third explicit human refusal despite the OFAC and EU sanctions lift.
- 2026-03-03 — Company Responded. Mercury's compliance team responded via compliance@mercury.com to the unblocking request, stating that Syria remains on Mercury's Prohibited Countries list and that the company is not able to provide services to users in Syria at this time. This is the third human response from Mercury maintaining the same position despite the OFAC and EU sanctions lift.
- 2026-02-26 — Company Responded. Mercury's compliance team responded to the fourth outreach via an automated email from compliance@mercury.com. The response acknowledged receipt of the request and assigned it Zendesk request #2082602, indicating it would be reviewed. The response appears to be an automated acknowledgment rather than a human review, as it arrived within seconds of the outreach and contained generic language.
- 2026-02-26 — Follow-up Sent. A fourth outreach email was sent to Mercury's compliance team at compliance@mercury.com requesting a formal compliance review to restore access for users in Syria. The email included a detailed legal annex referencing the December 2024 OFAC General License 24, the February 2025 EU Council Regulation 2025/167, the BIS License Exception SPP, and OFAC FAQ 1188. It also noted that major platforms including Stripe, GitHub, Google Workspace, and Cloudflare have already resumed services.
- 2026-02-24 — Company Responded. Mercury's compliance team responded via an automated email from compliance@mercury.com acknowledging receipt of the inquiry. The response appears to be an automated Zendesk acknowledgment rather than a human review, providing no specifics on whether the request would be reconsidered.
- 2026-02-24 — Follow-up Sent. A community volunteer escalated Mercury's case by emailing both compliance@mercury.com and privacy@mercury.com after two prior outreach attempts received explicit declines. The follow-up included a detailed compliance review request with a legal annex referencing the updated OFAC framework and BIS License Exception SPP, urging Mercury to reconsider its position.
- 2026-02-18 — Note. Mercury has now declined access twice within two days (February 16 and 18), with two different support representatives confirming the decision is final and cannot be reconsidered. Both responses were human-reviewed, not automated. Further outreach to Mercury's standard support channels is unlikely to yield different results — escalation through alternative channels (e.g., executive contacts, public advocacy, or partnership introductions) may be needed if this service is to be revisited.
- 2026-02-18 — Declined. Mercury's support team sent a second human-reviewed decline in response to the follow-up outreach on the same day. The representative stated via Zendesk that the onboarding team reviews each application by hand and that the application was denied based on internal factors. Mercury explicitly confirmed they are unable to provide more details on the denial reason and are not able to reconsider the decision.
- 2026-02-18 — Company Responded. Mercury's automated Zendesk system confirmed receipt of all four follow-up outreach messages, generating support tickets. The auto-replies stated that the support team would follow up within one business day. No human response has been received yet — these are standard automated acknowledgments, not substantive reviews.
- 2026-02-18 — Follow-up Sent. Two community volunteers sent follow-up outreach emails to Mercury at support@mercury.com and help@mercury.com on February 18, two days after Mercury's explicit decline. The emails referenced the 2025 OFAC and EU sanctions lift, cited unblocksyria.com resources, and requested a compliance review to enable banking services for Syrian users. Four separate support tickets were opened across two Mercury email addresses.
- 2026-02-16 — Declined. Mercury's support team sent a human-reviewed response denying the account application, stating that they are unable to support the account at this time. The representative confirmed that this decision is final and cannot be reconsidered, regardless of additional documentation provided.
- 2026-02-16 — Company Responded. Mercury's automated support system confirmed receipt of the outreach request. The auto-reply noted the message was received outside of regular business hours and that their support staff would review it as soon as possible.
- 2026-02-16 — Contacted Company. A community volunteer emailed Mercury at support@mercury.com requesting an executive-level compliance review to enable service access for users and businesses in Syria. The email cited the 2025 OFAC and EU sanctions lift and included supporting documentation from UnblockSyria.
- 2026-02-16 — Investigated. Community report from Syria via Android mobile (Facebook in-app browser). Mercury is a US digital banking platform known to block access from sanctioned countries. The submitted evidence shows only the Mercury app icon; blocking status requires further verification. (evidence: https://api.unblocksyria.com/files/evidence/k7krgbbxcg8jjbc69310fl4w/h8ej8xv3a1f9fb6alhwh7ehp-inbound5681505188599763231.jpg)

## Context

These are geo-restrictions the companies applied themselves, not filtering by Syrian ISPs and not a legal requirement. US and EU sanctions on Syria were lifted in 2025. See https://unblocksyria.com/llms.txt for the regulatory summary and https://unblocksyria.com/en/about for citations to the specific orders and regulations.

## Machine-readable

- JSON: https://api.unblocksyria.com/services/mercury?locale=en
- Timeline JSON: https://api.unblocksyria.com/services/mercury/timeline?locale=en
- HTML: https://unblocksyria.com/en/services/mercury
- Other languages: https://unblocksyria.com/ar/services/mercury.md, https://unblocksyria.com/ku/services/mercury.md