Data last synced:
Last updated:
American Express National Bank ("Amex"), a subsidiary of American Express Company that provides charge and credit card products and travel-related services to consumers and businesses, settled for $430,500 to resolve 214 apparent violations of the Foreign Narcotics Kingpin Sanctions Regulations. Over the course of two months, Amex processed transactions for an account whose supplemental card holder was designated in connection with illegal drug distribution and money laundering, enabling $155,189.42 worth of transactions through a combination of human error and sanctions compliance program deficiencies. The settlement amount reflects OFAC's determination that the apparent violations were not voluntarily self-disclosed and were non-egregious.
Penalty Amount
$430,500.00
Enforcement Date
July 15, 2022
Rank in Top Penalties
#149
On November 16, 2012, Walter Alexander Del Nogal Marquez ("Marquez") applied for and obtained a supplemental American Express Centurion Card on an account maintained by a U.S. person at Amex. On May 7, 2018, OFAC designated Marquez pursuant to the Foreign Narcotics Kingpin Sanctions Regulations (FNKSR), 31 C.F.R. Part 598, and added him to the SDN List. A few days after designation, Amex's internal sanctions list screening system generated a "high confidence" alert. An operations analyst erroneously closed the alert despite a match against multiple data elements โ name, date of birth, and Venezuelan National ID number โ and an internal procedural requirement for a second-level review of all high-confidence alerts.
On June 26, 2018, an analyst investigating an anti-money laundering ("AML") media alert identified and escalated Marquez's connection to the account. Instructions were given the following day to suspend charge privileges on all cards linked to the U.S. person's account, including Marquez's supplemental card. However, the employee who entered the suspension code did not include comments indicating the restriction was sanctions-related. When the U.S. person accountholder called on June 28, 2018 to inquire about the account status, a customer care professional removed the suspension. The AML team caught the error the next day and directed the account to be re-suspended, but the team applied the incorrect suspension code, allowing seven additional transactions after the suspension was lifted before the account was closed on July 6, 2018.
In total, between approximately May 7, 2018 and July 6, 2018, Amex processed 214 transactions totaling $155,189.42 in apparent violation of the FNKSR, 31 C.F.R. ยง 598.202.
OFAC determined that Amex did not voluntarily self-disclose the Apparent Violations and that the Apparent Violations constitute a non-egregious case. The statutory maximum civil monetary penalty applicable in this matter is $331,288,050. Under OFAC's Economic Sanctions Enforcement Guidelines, 31 C.F.R. Part 501, app. A., the base civil monetary penalty amount equals the sum of the applicable schedule amount for each apparent violation, totaling $574,000. The settlement amount of $430,500 reflects OFAC's consideration of the General Factors under the Enforcement Guidelines.
This action highlights the importance of properly training employees on sanctions compliance procedures and ensuring that those procedures are followed appropriately, especially when high-confidence alerts are generated. Consistent application of enterprise-wide compliance measures, including controls to prevent other departments or personnel from overriding a sanctions-related decision to suspend an account, can also help mitigate the risk of a sanctions violation.
This page summarizes an OFAC enforcement case based on the document archived below. SanctionsLookup assumes no liability for errors, omissions, or inaccuracies in the original documents, this summary, or any changes made to the source documents at any time.
Provided for informational purposes only and does not constitute legal or compliance advice. Always consult the source document directly rather than relying on this summary.
Archived on June 13, 2026
SHA-256: f8ead363eef055908efd24f574ea46dab66cc6f19b7dd4a21220fa11b732723d