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
- 9122a2997cb347dccf77f14e31dd2287f888528b91c5edb31a475ae469bd5b83
- request
- 3095415c96051e49dca6edfdbb026349591834c93a6426d26883e97d11f6b6ab
- transaction
- 58c44b594af59300629b39de89c937de14820cbb2b6a67d7220b639bd8c79f13computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46432
the chainentry 46432
- sealed to the entry before
- 0cf93481e7e8f1b668dd37e4aca147014cd68b9a14a389f99fc26f4b5fe009b2
- this leaf
- 9c0fd0b1092079f57989299963d0b8c09b307f7e4ca866ba286e9c0ac68e46e6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Cf8LbBSo3RersP+eLn1sH/EjCGyXcA9mA5byLuhSvJSXk3f8NYFuylHZyxb1I2iA+IfDhKBiv0abM8Y2aUgSCw==