OFAC screening overview

the office of foreign assets control (ofac) is a financial intelligence and enforcement agency of the us treasury department ofac compiles a list of individuals and organizations who may present security and criminal risk to society they do this to enforce economic and trade sanctions in the united states those entities are forbidden to make financial transactions in the us the ofac list enables financial institutions to monitor and restrict the use of their services to entities on the list individuals or organizations who are on the ofac list may include terrorists, politically exposed foreign officials among other criminals why do cross river merchant partners need ofac api function calls? cross river enables and supports ofac api calls to comply with sanction screening obligations partners need to meet these requirements when executing monetary transfers that include non us countries why are ofac api function calls important? both the us and canada administer and enforce economic and trade sanctions they base these sanctions on foreign policy and national security goals as such, both countries take measures against a range of targets that include foreign countries and regimes terrorists international narcotics traffickers those engaged in activities related to the proliferation of weapons of mass destruction other threats to each country's national security, foreign policy, or economy it is strictly prohibited to do business with countries or entities on an ofac list likewise, it is forbidden to facilitate financial transactions to or from individuals, entities, or countries on these lists ofac violations can result in severe civil and criminal penalties! when does a merchant partner call the ofac endpoint? if a cross river merchant partner wants to perform international transactions, they need to execute a function call to the ofac endpoint before the transaction request what do the ofac screening endpoints do? the ofac screening endpoints perform ofac screening to a specific cardholder the endpoints respond with the ofac status to the partner suppose the partner wishes to perform international transactions the card payments gateway validates the international transaction recipient sender pair with recent ofac calls that is how the gateway verifies the validity of the pair let’s say the cardholder was not scanned recently for a transaction or was scanned but was not validated in that case, the gateway will reject the international transaction, providing the reason for the rejection api reference see our ofac docid\ sid2vnamxnpf3p5ruofw1 these are the function calls that let you verify ofac compliance, get screening status, and get scan id