Non-Payment
The NPA Rule controls how non-payment authentication transactions are handled. NPA transactions validate a cardholder's identity without involving a purchase - the 3DS Requestor communicates with the ACS to verify the cardholder without a financial transaction taking place.
Common non-payment use cases include:
Verifying the cardholder's identity when adding a card to a digital wallet.
Verifying the cardholder when adding a merchant to their Whitelist.
Validating identity during account registration without a payment.
The rule allows you to define separate outcomes (accept, challenge, or deny) for individual NPA transaction types.
When the action is set toDeny, the transaction is not rejected - it is passed to subsequent rules for further evaluation.
Flow
flowchart TD
classDef success fill:#e6ffed,stroke:#38a169,color:#276749
classDef terminal fill:#fff5f5,stroke:#fc8181,color:#c53030
classDef process fill:#ebf8ff,stroke:#4299e1,color:#2c5282
START([Transaction received]) --> CAT{Is non-payment<br/>transaction?}:::process
CAT -->|No| NEXT([Next Rule])
CAT -->|Yes| ACTION{Configured action?}:::process
ACTION -->|Allow| ATYPE{Matches<br/>transaction type?}:::process
ACTION -->|Challenge| CTYPE{Matches<br/>transaction type?}:::process
ACTION -->|Deny| DTYPE{Matches<br/>transaction type?}:::process
ATYPE -->|Yes| ACC([Frictionless · SUCCEEDED]):::success
ATYPE -->|No| NEXT2([Next Rule])
CTYPE -->|Yes| CHAL([Challenge Flow]):::process
CTYPE -->|No| NEXT3([Next Rule])
DTYPE -->|Yes| NEXT4([Next Rule])
DTYPE -->|No| ACC2([Frictionless · SUCCEEDED]):::success
Examples
Accept Add Card Transactions
Non-payment transactions of the Add Card type are approved frictionlessly.
Deny Specific Transaction Types
Exemptions are denied for Split Shipment and Cardholder Verification transaction types. These are passed to subsequent rules rather than rejected.
Challenge Specific Transaction Types
Non-payment transactions of the Maintain Card type are sent to the Challenge Flow.
Updated 18 days ago