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
- 18689e82b6d2e442504a4f487f385fc01f64228c0c498676afce19b1b8632372
- request
- bf50a95a10c5aa5e9671db268e609f9b416df25b8f55eddf23d93db715a66b7d
- transaction
- 5174af399659650a9be63626d4c279d79e70244a70535662ab83a334d1d853b1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75426
the chainentry 75426
- sealed to the entry before
- 02888338eeec845ccf3884178af9ba4c81e0c2558c9a543e02b345226bd2c576
- this leaf
- 9b9ba85b22eb176844ea81a879be78e8e65b0a2b43623274d463a7e15fa9db03
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eqtLSSG49oKxDNfJW+sKFf+SE66P13xNO2HlekVphe3CKSun2JjjGA6zas21W2JfvrnFlxfQiWBQqUi6yzXmAQ==