why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- f954d19c165a4741ba160440ab8fdd8e26c94d9f8128298e7127032fa1c7e183
- request
- 536c5b2b0d704cff20ad8313c69d66de16c87015077c571648d28ebfd04028ce
- transaction
- c0eb36413d4174ee12e9e0c28b6b319ca88184348a3367930390c867e555c944computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10028
the chainentry 10028
- sealed to the entry before
- 5dfa637eabbb3169fd9fa22cc1216bdd1502f3ab9a67107bc6e4d5e557733cca
- this leaf
- 0d9440ef45cb2dc4d91fe8ff9954d1a071172b3ee26be609e447cd12d5de4b73
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qMnDD2ipqxHCNJFQmrWi/LEkqKRN2YPNA3eKs5nO5dADJDpOHueucfzoPatKd4d5q4FSUO0ZnNnJLCVpRERNDA==