Blocklists

Use blocklists to prevent fraud and criminal activity. Blocklists are lists of customer attribute values that are blocked from buying from you. For example, if a customer attempts to make a purchase from you with a credit card or fingerprint that is in a blocklist, the transaction is blocked and will not be processed.

Before a new transaction is processed in Rebilly, blocklists are examined to check for attributes related to the entity. If a match is detected, the operation is aborted.

Rebilly provides the following blocklist attributes:

  • Customer IP address: IP address of the customer making the purchase.
  • Customer email: Email address of the customer making the purchase.
  • Customer ID: Rebilly customerId of the customer making the purchase.
  • Payment card: Payment card number being charged.
  • Payment card BIN: The Bank Identification Number (BIN) of the payment card being charged.
  • Device fingerprint: A string holding information about the software and the device used by the customer making the purchase.
  • Country: Country where the customer is making the purchase, and of the payment card billing address.

Create a blocklist

This process describes how to create a blocklist for a specific email address. All actions and events associated with this email address will not be processed in Rebilly for a set period of time, or permanently if you choose it.

  1. In the left navigation bar, click automation icon Automations , then click Blocklists .
  2. Click Emails , then click Add blocklist item .
  3. In the Email field, enter the email address that you want to block.
  4. In the TTL (Time to Live) field:
    • To create a temporary entry, enter a value in seconds.
    • To create a permanent blocklist, enter 0 or leave this field blank.
  5. Click Save blocklist item .

View active blocklists

  1. In the left navigation bar, click automation icon Automations .
  2. Click Blocklists .

Create event based blocklists

To automatically add customer attributes to blocklists when specific events occur, see Blocklist actions.