In the iGaming, betting, and lottery industries, processing transactions with cards issued by banks that restrict gambling activities leads to immediate transaction declines, wasted gateway request fees, and potential processor penalties. The GAMBLING_BLOCKED parameter helps merchants and payment gateways filter out restricted BINs before sending requests to the acquiring bank.
| Supported Values: TRUE (gambling transactions are blocked by the issuing bank or network) or FALSE (no gambling restrictions flagged for this BIN). |
| Integration Purpose: Allows checkout systems to proactively hide payment methods or warn users, preventing failed authorization loops. |
| Custom Database Build: Available as a dedicated extra parameter flag in your custom BIN database package. |
See how the gambling restriction flag optimizes your transaction flow:
Support for Gambling Blocked identification is available as an optional add-on for custom database builds.
| Feature | Capability |
|---|---|
| Parameter Name | GAMBLING_BLOCKED |
| Possible Values | TRUE / FALSE |
| Integration Format | Additional column in CSV/JSON custom database exports. |
This data is available at additional cost of $800 (one-time).
For technical inquiries regarding Gambling Blocked data mapping:
Contact Engineering Support
