Main navigation

Error message

Warning: Undefined array key 0 in amp_entity_view_alter() (line 156 of modules/contrib/amp/amp.module).
amp_entity_view_alter(Array, Object, Object) (Line: 545)
Drupal\Core\Extension\ModuleHandler->alter('node_view', Array, Object, Object) (Line: 304)
Drupal\Core\Entity\EntityViewBuilder->buildMultiple(Array) (Line: 238)
Drupal\Core\Entity\EntityViewBuilder->build(Array)
call_user_func_array(Array, Array) (Line: 111)
Drupal\Core\Render\Renderer->doTrustedCallback(Array, Array, 'Render #pre_render callbacks must be methods of a class that implements \Drupal\Core\Security\TrustedCallbackInterface or be an anonymous function. The callback was %s. See https://www.drupal.org/node/2966725', 'exception', 'Drupal\Core\Render\Element\RenderCallbackInterface') (Line: 788)
Drupal\Core\Render\Renderer->doCallback('#pre_render', Array, Array) (Line: 377)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 204)
Drupal\Core\Render\Renderer->render(Array, ) (Line: 238)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}() (Line: 583)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 239)
Drupal\Core\Render\MainContent\HtmlRenderer->prepare(Array, Object, Object) (Line: 128)
Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse(Array, Object, Object) (Line: 90)
Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray(Object, 'kernel.view', Object)
call_user_func(Array, Object, 'kernel.view', Object) (Line: 111)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch(Object, 'kernel.view') (Line: 187)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 191)
Drupal\page_cache\StackMiddleware\PageCache->fetch(Object, 1, 1) (Line: 128)
Drupal\page_cache\StackMiddleware\PageCache->lookup(Object, 1, 1) (Line: 82)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle(Object, 1, 1) (Line: 704)
Drupal\Core\DrupalKernel->handle(Object) (Line: 18)

FATF Now Requires Cryptocurrency Exchanges to Share Their Clients’ Data

Advertisement
Fri, 21/06/2019 - 18:41
FATF Now Requires Cryptocurrency Exchanges to Share Their Clients’ Data
Cover image via U.Today
Read U.TODAY on
Google News
Advertisement

The Financial Action Task Force (FATF), an international organization that strives to combat money laundering and other illicit activities, has recently ruled that global cryptocurrency exchanges now have to share personal information about their clients, Coindesk reports.

This applies to a situation when one has to transfer money from one exchange to another.

Related

Advertisement

Your name, please?

This rule is nothing new in the world of traditional finance since it applies to international banks that also exchange their customers’ data to mitigate risks.

From now on, crypto exchanges (they fall into the “virtual asset service providers” category) are required to accompany each transfer with the originator’s name, account number, physical address, etc.

FATF offers a list of recommendations on how to enforce these requirements. The most interesting part concerns the clampdown on various services that are able to hide the sender of the funds.

Those users that end up on the ‘bad guy’ list should be barred from performing any transactions.

Related

Keeping them in check

If a certain country stubbornly refuses to comply with FATF’s requirement, it appears in serious danger of being blacklisted by the organization, thus becoming toxic for investors. Case in point: Iran.

According to FAFT, those exchanges that don’t follow the rules should be prohibited from conducting operations.

“If the VASP cannot manage and mitigate the risks posed by engaging in such activities, then the VASP should not be permitted to engage in such activities,” the document states.

As reported by U.Today, the FATF first announced its intentions to draft a set of rules for crypto exchanges as a means of preventing money laundering and terrorism back in September 2018.

Related articles

Advertisement
TopCryptoNewsinYourMailbox
TopCryptoNewsinYourMailbox
Advertisement
Advertisement

Recommended articles

Latest Press Releases

Our social media
There's a lot to see there, too

Popular articles

Advertisement
AD