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
- 1dd64a4829534cbe396856616e888ff944141b195d2a447f9a496571ab22f129
- request
- 20bd3bb4356e0ee64113fe1ce22afd62d25b9c407d730e2c82808647791eb547
- transaction
- 21ed5d504a5e4697fabbc60dc7e518daa795efe8a89034ba3490b2d069c53933computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6581
the chainentry 6581
- sealed to the entry before
- 18871fd88ea0f06a4b3118ebbf3ea63aa10255db8ae9d9ffa1bf15d4f1514325
- this leaf
- ce7669e9a734d00224021ba80a5efee81220ba103092e8aa5267783fef33b483
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- enYt5hICeQ+JZU4xMYDW84bXmiRPiWhdfGfBQitQ28kdX5Km3l46AgXyqM4tHfJ/WB/DpJYmZGpguZjqVxwyCg==