Is My Country Supported for Payouts via Efty Pay?

Efty Pay is committed to providing seamless payouts to domain sellers around the world. While we strive to support a vast range of countries, there are certain locations where payouts are currently unavailable due to regulatory restrictions.

The following countries are not supported for payouts at this time:

  • AF - Afghanistan
  • BY - Belarus
  • CD - Congo (the Democratic Republic of the)
  • CF - Central African Republic (the)
  • ER - Eritrea
  • ET - Ethiopia
  • IQ - Iraq
  • GN - Guinea
  • LB - Lebanon
  • LR - Liberia
  • LY - Libya
  • ML - Mali
  • RU - Russian Federation (the)
  • SD - Sudan (the)
  • SO - Somalia
  • SS - South Sudan
  • UA - Ukraine
  • VE - Venezuela (Bolivarian Republic of)
  • YE - Yemen
  • ZW - Zimbabwe

Why Are These Countries Not Supported?

At Efty Pay, our priority is to guarantee the integrity of transactions conducted using our services. This means adhering to global regulations and compliance requirements set by our payment processors. Certain countries have specific restrictions and prohibitions that prevent us from supporting payouts at this time.

We want to emphasize that this decision is not based on our unwillingness to support sellers from these countries, but rather in accordance with relevant regulations. Our payment processor ensures that all transactions meet global compliance standards, which may result in limitations for certain regions.

Our Commitment to Global Support

At Efty Pay, we are continually working to expand our reach and hope to be able to support sellers in every corner of the globe, including those currently not supported. As we monitor regulatory changes, we remain optimistic about the possibility of offering payout services to these countries in the future.

Please don’t hesitate to reach out to our support team if you have any questions regarding payouts or your country’s eligibility. We are here to assist you in any way we can!

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.