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
- 22ce67a9ca1d7f39393e2ff8cac9680ba4ec7151cfac0cba5a193c0b009022dd
- request
- 0c1bf510c305e621f0640818427e470f4132feb4c70fc0f782780b512ee4c69a
- transaction
- 24adc597e850b938ee664e6a964a6890873ec2a3c81b74837346101292a752accomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48033
the chainentry 48033
- sealed to the entry before
- 44adac519bbad4f6eada4e1cbab1edfc331a5808b1c412bce3e6f6ebf268a010
- this leaf
- da4be4df44a18af9872679563d9be5a7ff6025e83f7376463dedda44798a33df
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /8ehRBYerNMjY7MS+Dca/kxl551FOgXivFbEL+jbyLpFv8m7JAfrraZ3klsvfU4LeVktZ28O8SoBnLTUiZOlDQ==