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
- 0d2ceb61b3b23fda8eaf76c0b30d26945044512603d645f67ba017c30e944239
- request
- 15e4f221d4fad2b573c2aa04b4f79a37082e05dea8861d61c981870debfd5c42
- transaction
- ab7092713216675bb1caed954b2160f0d6f51a2f4b5d4453ad47748255273d2ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2110
the chainentry 2110
- sealed to the entry before
- a38091051d717f96d8cb5ba5e48b357203f1fb862c60431bf5f95038b029559f
- this leaf
- 6a81e8f0dc2f12cdd974cc1b40fc3d5c7a28b57947c4a90a11881f2094d77718
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2oLjxAmbZhDEWLhOPznqDqddGVfv0lM98XgUq+HI8FNl58RxzHmfkNwgRS5dCh6yLYPJSvUz/DxPZhXIQJU8Cw==