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
- fa1172c444ef6e6b81711445270e247d331271dcdae556a54fda28838fb76cd0
- request
- d3d97df3ce368a969f47d3003258942dcdc5779c4eee3fa6c80ef98bd4b554c2
- transaction
- 904e952d5e0dcf328e997d77c8129e5d7220f7da8621f5959ab43cecb047593dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52752
the chainentry 52752
- sealed to the entry before
- e382fcd97bb8f9176f14f73efa46485b3b6f5fe7789527d08623e2bf7c3c2a80
- this leaf
- 74d39756db6db4e9676f3e83b9077fe3ce6b652c2243d9c9c86d9ed8299ab01d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gKiG1pYd0NmXDvnWxkIozco5yn+nY4XgQTwBTAhp32dIBP1zAeYOgppY/sdAYTZ/bc7X/Xr5NhN9uuCbuLvdDA==