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
- bea05ee600fec38357f918899a74b1f8d8438f84666369c3cf89580da3663810
- request
- 03193d27fca7c04895357088bb1452e1851d4d54b9055f5fcfdfad6d0a37f54b
- transaction
- 3bfc4ebf96de6341d2b42f49a9f6ac5ed817a832e22b79a67086834238c31fa3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64063
the chainentry 64063
- sealed to the entry before
- a0ec021faf9d5e4973ea3ab8e8aeefe9f7b4e31567e3608c9095662b433b83bb
- this leaf
- 897c994cdcddb10b180309893bbc30e12a48f9acd3ea1241f8a29787324e182b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5HQ9ZCVzw/5+4pOYQHJ7pTyHD8asItCLW7ufGhbSxHFgQ8U8AJIB/K3YQyGR5zkJouYrLKXmHxdG9XPNailhCA==