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
- e8cf710b06774789a8e67131f8a0b7f89f8365a8bcca5ec9ee1819080bad00b7
- request
- b13002b52bf98f5b976daf2d13ed89d3f9b6892565c68ec9b6b6c3ed446ccf2a
- transaction
- fcbdd9157548edd860a7a4b8939ad6ceee62ef48a88f00718ece8c495eee659ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31319
the chainentry 31319
- sealed to the entry before
- c0272576bd10bb70300cd4928152bd039fd9f62e6eeba9d6788a99f102bcae84
- this leaf
- 57c99f4ae8e840baff9d3d2ac389c586124c739c4d38310e1ab8cf94a132102e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5V5UnVtIx6KsgK/u0aughNrnRyA99+a5drRual3ICXbmsDSMdVv7yUQRHYJFb5ffqfALWlDSGhq7H+yr4se/CA==