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
- 63477e569b397f04e48059fabfa65bcb2e5e61860bd1a38b631daa558c50980e
- request
- 145692684c081fe34d55b893325245ad68c8fb75529bb7f154ec6e0a493cd849
- transaction
- 680606ce5e240dd3dba4b6432e826e3949ec51994a5c02d8dd00f4cfebc6fa50computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45890
the chainentry 45890
- sealed to the entry before
- 4e70fb44445382c65a291ceaf81f3cd54fb3f683d400d5615a44990cc5ace2a0
- this leaf
- 894fbef810023c7b0cea8a3e1c6ae930f7d2b11e9b1fd7930daa2a855fda34ef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3QijEwqJHRJTgbZHW0qViFjmQh2iuSiIIAWevWm4+7OUED3BPqcSgIye9YekLiggwYYsG1I9fj7PqJB76lU3Dw==