Overview
As an international payments company regulated in multiple jurisdictions globally, Transaction Monitoring is an important part of Currencycloud’s anti-money laundering and financial crime prevention framework.
The purpose of our Transaction Monitoring function and processes are to:
- Identify and block transactions from/to sanctioned individuals, entities, or countries.
- Identify and remediate transactions and patterns of behaviour potentially connected to money laundering, terrorist financing, or other financial crime.
- Investigate transactions and patterns of behaviour to ensure they are consistent with our knowledge of the client, its business, and our risk appetite.
- Make decisions on transactions that alert for manual review and on potentially suspicious patterns of behaviour.
Transaction Monitoring at Currencycloud is separated into two distinct areas:
- Real-time screening of transaction fields connected to the client and transaction against various checks. Responding to real-time requests for further information on individual transactions (which have not yet been executed) from our banking partners.
- Retrospective monitoring of account behaviour to identify patterns of potentially suspicious activity. Responding to retrospective requests for further information on an entity’s transactional activity from our banking partners.
Note: After we have responded to a request for information from a banking partner, we are unable to ask for a status update on the transaction for a certain number of working days. This period of time varies by banking partner but in some cases can be up to 5 working days.
Our Transaction Monitoring function consists of two sub-teams, one focusing on real-time screening and the other on retrospective monitoring. More information and FAQs below.
Real-time screening vs. retrospective monitoring
Real-time screening |
Retrospective monitoring |
|
---|---|---|
What do our systems screen/monitor? |
All transactions into and out of the Currencycloud ecosystem for all entities are automatically screened in real-time against various controls and checks. |
All transactions into and out of the Currencycloud ecosystem for all entities (companies and individuals) are automatically monitored against various controls and checks. |
When does this take place? |
This screening happens before an inbound fund (receipt or collection) is credited to the client account or before an outbound payment is submitted to the banking network. |
This monitoring happens post-transaction: after inbound funds have credited the client account or outbound payments have been submitted to the banking network. |
What can the outcome be? |
Transactions can either:
Alerts are manually reviewed by a Compliance Specialist. Transactions are then ultimately either manually approved, manually rejected, or held for further review. |
The activity of some entities may create an alert. This means the transactional behaviour of an entity needs to be investigated by a Compliance Specialist. Alerts are reviewed and in some cases we may subject the entity to enhanced due diligence or even off-board the entity. |
How do we review transactions that have alerted for manual review? |
Where possible we aim to resolve alerts internally - using our knowledge of the entity in question, their previous transactions, the expected behaviour of other clients in that segment, and any KYC information or documents we already have on file. However it’s important to note that sometimes Currencycloud only has visibility of a certain part of an entity’s activity. As our client (either regulated or unregulated), you may have more information from your relationship with the entity. So in some cases the real-time/retrospective team will need to request further information to resolve an alert. Clear and comprehensive information in response to our request always helps our teams resolve alerts as quickly as possible. If there’s any other information you’d like to provide in addition to what we request, please do share this with us - making it clear what the information is and how it supports your answer to the query. |
FAQ
Question |
Answer |
---|---|
What are the main questions Currencycloud needs to get comfortable with when reviewing a transaction that’s alerted for manual review? |
|
What are the main types of information and documentation I could be asked to provide? |
|
How can I provide documents before I submit a transaction (e.g. high-value transactions)? |
Documents can be sent to kycrequests@currencycloud.com. When sending the documents, please make it clear who the transaction relates to (e.g. account IDs, transaction IDs). Specific guidance on how to manage large transactions can be found in the Help Centre article here. |
If I proactively provide documents in advance, does that mean I won’t receive any further requests for information on that transaction? |
No. Sending documents in advance doesn’t guarantee that we won’t need to request further information at a later stage. Proactively sending documents simply means that we skip a step in the transaction review journey because you don’t have to wait for the initial request for information from us. If a transaction has alerted for manual review it will be reviewed in light of previous transactional behaviour, any information we have on file, and any documents you might have provided in advance. But if further information is required, this will be requested. |
Do some transactions get escalated? |
Yes. Depending on the risk profile of a transaction it may be escalated to more senior members of our Compliance function. Our real-time screening team makes every effort to do as thorough a review as possible before escalating. But each transaction is judged on its own merits and the individual reviewing the escalation may ask that the real-time team request further information from you so they can make a decision on the transaction. |
What types of transactions or entities are likely to receive greater scrutiny - and may result in requests for further information? |
|
If a transaction is manually rejected, can you tell me why? |
This can be a sensitive area and there is a limit to how much information we can share. We are able to share that the transaction has been rejected because:
If you’re a regulated client then, on a case-by-case basis, we may share more information with you on the specific concerns we have - so that you can take appropriate action. |
How can I provide a good response to a request for further information? |
|