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
- a80ad1202d152b2b27649f565153e228400ae970faa0a124b13f736eba2f4d35
- request
- d48d892853e98d61773e4619808671610e8a74c7cc97519b8c2bb1d666f1b5bf
- transaction
- 6c40cfaf2967dccc0a7348981b13ef1f0606ea9362662ea86a11d62135698769computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5067
the chainentry 5067
- sealed to the entry before
- f00a05b88615b59332e0692aae54f8cf446cc759f58f4e41b52d50bdd7802d18
- this leaf
- 138c365e87af51444ca26143b732fd0dd8013f56767c068185f2047208ec65f5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /gmbQj7fSZWASvQTOWpWynLto8U8dEVfNiiaLGTg9pUWsPoeWjjb7gGFAAoNYSifUIOXJJnbskYemderXpD6Ag==