How to Enable and Use Blocked Cards for Credit-Card Risk Control

Introduction

This guide shows you how to configure and use the Blocked Cards feature to flag risky credit cards, warn cashiers during payment, and keep an auditable record of chargeback-related cards. You’ll learn how to:

• Add a card to the blocked list from an online receipt on BLogic View
• Manage blocked cards in BLogic View (add, edit, delete, export)
• Understand warning behaviors in POS for Manual Entry and PAX Terminal flows

Why it matters: Early warnings help your team recognize suspicious transactions, reduce fraud exposure, and standardize handling procedures.

Version Support: v7.2025.11.12

---

Table of Contents

1. Add a Card to Blocked List from Transactions
2. Manage Blocked Cards in BLogic View
   • 3.1 Search & Filter
   • 3.2 Add New Card
   • 3.3 Edit or Delete
   • 3.4 Export & Print
3. POS Warnings & Cashier Flows
   • 4.1 Manual Entry Flow
   • 4.2 PAX Terminal Flow
4. Business Rules Matrix
5. FAQ

---

1. Add a Card to Blocked List from Transactions

Use this when reviewing an online receipt for a ticket paid by credit card.

1. Open Transactions Module → open the receipt view of a credit-card ticket.
   • The button “Add To Blocked Card” appears only if the ticket was paid by Credit Card.
2. Click Add to Blocked Cards.
3. A Confirm Dialog appears (Confirm Add to Blocked Cards) showing:
   • First 6 digits, Last 4 digits
   • Last Ticket# Chargeback (pre-filled if available)
   • Last Date Chargeback
   • Note (optional)
4. Review or edit details → click Add to save (or Cancel).
5. On success, the card is added to the Blocked Cards database, immediately affecting POS warnings.

Tip: Use the Note field to record reason/evidence (e.g., chargeback case ID).

---

2. Manage Blocked Cards in BLogic View

Go to Setup → Blocked Cards.

Table Columns

• Date Added
• Card Number (masked, e.g., 1234 56xx xxxx 4123)
• Last Ticket# Chargeback
• Last Date Chargeback
• Note

Add New Card

1. Click Add New.
2. Enter First 6 Digits, Last 4 Digits, Last Ticket# Chargeback (optional), Last Date Chargeback (optional), and Note.
3. Click Save.

Edit or Delete

• Select a row → Edit to update fields or Delete to remove the record.
• Confirm the action in the dialog.

Export & Print

• Click Export or Print to get a hard copy for audit or offline review.

---

3. POS Warnings & Cashier Flows

When a card matches Blocked Cards, POS displays a warning dialog with standardized options. Staff must confirm they’ve read the warning.

Manual Entry Flow

1. Choose Credit Card → click Enter Card# Manually.
2. Enter Card Number → click Pay.
3. Before processing, POS checks Blocked Cards:
   • If matched, show warning with options:
     • Continue Payment & Print Authorization
     • Continue Payment (Verify ID if needed)
     • Cancel & Choose New Payment Method
4. Cashier decides to proceed or cancel.

PAX Terminal Flow

1. Customer pays on PAX (tap/swipe/insert).
2. After a successful approval, POS checks Blocked Cards using PAN data returned by PAX.
3. If matched, show warning with options:
   • Accept Payment & Print Authorization
   • Accept Payment (Verify ID if needed)
   • Void Payment & Choose New Payment Method
4. Staff confirms they have read the warning.

---

4. Business Rules Matrix

Scenario	Behavior	Result
1. Card in blocked list – Pre-auth	Check list + show warning	Do not allow Pre-auth
2. Pre-auth completed, card later blocked – Capture	No additional check	Allow Capture
3. Card in blocked list – Void/Cancel Ticket	No blocked check	Allow Void/Cancel
4. Deposit Payment with blocked card	Check list + show warning	Do not allow Deposit Payment
5. Add/Edit Tip in Batch Manager	No blocked check at tipping time	Allow; warnings happen at Payment/Pre-auth
6. Cancel/Void Pre-auth for a now-blocked card	No blocked check	Allow Cancel/Void Pre-auth
7. Partial Refund on ticket paid by blocked card	No blocked check	Allow Partial Refund

Policy: Blocking a card affects payment attempts; it does not prevent back-office actions (voids, refunds, tip edits) needed for operations and compliance.

---

5. FAQ

1) Can a blocked card perform Pre-auth?
No. The system checks the list and shows a warning; Pre-auth is not allowed.

2) If a card was Pre-authed and then gets blocked, can I still Capture?
Yes. Capture of a previously approved pre-auth is allowed (no re-check).

3) Can I Void/Cancel a ticket paid with a blocked card?
Yes. Voids/Cancels are allowed without additional blocked-card checks.

4) Can I pay a Deposit with a blocked card?
No. Deposit payments trigger the check and are not allowed for blocked cards.

5) Does blocking affect adding or editing Tips in Batch Manager?
No. Add/Edit Tip is allowed. Warnings occur at Payment/Pre-auth stages instead.

6) If I Pre-authed and the card is later blocked, can I Cancel/Void the Pre-auth?
Yes. Cancel/Void Pre-auth is allowed.

7) Can I do a Partial Refund on a ticket paid with a blocked card?
Yes. Partial Refund is allowed.