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
- 29cdde036c18be6394b7d22f65cfd8fb0e24ced7ca5fe20264823b6fc9c82d25
- request
- 377734a813a7b7d1d00d9e8223f800328d732ac7abaa7df018b78585b4dfdc8c
- transaction
- 2f7e36fd7c00627638685baf93c859171b9d5bda91807dea65d1c8ee121e1f7bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33216
the chainentry 33216
- sealed to the entry before
- d7858523fe4ca3e06525729c02c31e27968cea82680b39697bf305cfca819d54
- this leaf
- 7ae188b3d3f9871e0bc9fbc8416901fefa40bcd1546605cc5b3a586ff450af84
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- p5p5pxuqKNov6C8SJjHunoY4l8uKgHrBlAxThKWkVJEkwv3UYomf2DIpfpXlnjsyhbdbc+7IynkZsAu/AaQOBQ==