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
- 6edb6b992bcb1b40a89d24dd93cd0aa903efc6d443ad147cb12f21b9f92f9ea6
- request
- 7ba0bcbe02e27077e633cb3f3359992653702c53ac13e759023cc600c8681dea
- transaction
- 9365d8c46296fd5a34cbf599b5d86355c0ea4b17738bc403ce7183189655557ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20441
the chainentry 20441
- sealed to the entry before
- 0dc67eefd60da79127cb4f854743696efdcfbab5fb35e37befc96a541fb4510e
- this leaf
- d99d7a19f3e9f87a6894bee170df0ad88583015ebab589877f3aef4d5784e87a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OzfhY2iU4O/BY85aNdlh/GKjdIbGeki9ZqVVrKGWpdGIoTsDuP5xlP8hetPjaLnh6wA0MI2cxPvPCaHnz0PVCg==