Transaction Screening
WickiePay includes built-in AML/OFAC transaction screening to ensure all payments comply with regulatory requirements.
How It Works
Every transaction is automatically screened against sanctions lists and risk databases:
Transaction Created → Screening Engine → Result
↓
PASS → Transaction proceeds
FLAG → Manual review required
BLOCK → Transaction rejected
Screening Checks
| Check | Description |
|---|---|
| OFAC | U.S. Office of Foreign Assets Control sanctions list |
| EU Sanctions | European Union consolidated sanctions list |
| UN Sanctions | United Nations Security Council sanctions |
| PEP Screening | Politically Exposed Persons database |
| Adverse Media | Negative news and media screening |
| Blockchain Analytics | On-chain risk scoring (mixer detection, darknet, etc.) |
Screening Results
Via API
GET /api/v1/screening?transactionId=tx-uuid
Response:
{
"transactionId": "tx-uuid",
"status": "PASS",
"checks": [
{ "type": "OFAC", "result": "CLEAR", "score": 0 },
{ "type": "BLOCKCHAIN_ANALYTICS", "result": "CLEAR", "score": 12 }
],
"timestamp": "2026-01-15T10:25:00Z"
}
Screening Statuses
| Status | Action |
|---|---|
PASS | Transaction proceeds automatically |
FLAG | Requires manual review in WickiePay Backoffice |
BLOCK | Transaction automatically rejected |
Manual Review
Flagged transactions appear in the WickiePay Compliance Backoffice for manual review:
# Approve a flagged transfer
POST /api/v1/screening/{id}/approve
# Reject a flagged transfer
POST /api/v1/screening/{id}/reject
# Bypass screening (requires compliance role)
POST /api/v1/screening/{id}/bypass
Configuration
Screening thresholds and rules are configurable per merchant in the WickiePay Backoffice:
- Risk Score Threshold — Score above which transactions are flagged
- Auto-Block Rules — Conditions for automatic rejection
- Whitelist — Known trusted addresses that bypass screening
Next Steps
- Travel Rule — Crypto Travel Rule compliance
- KYC / KYB — Customer and merchant verification