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
- 49dd129182562c459e9fa21d63ba8d833da10cd9da83595453307de4ea051e35
- request
- 4cbe3113ce32b29ad10c2101a17438ee61057f18a811664823fb29c65d0cb351
- transaction
- 33b543a2114290b22b3bb6e437e0f6a8d7f1dd9e99833e7336a0838acf719e60computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75180
the chainentry 75180
- sealed to the entry before
- 2b0f2a4447cf745827d9c41f7f70ce0170f8038631c62184720ee40d61036f36
- this leaf
- 9c00b7c2780b6543864bff8d25843b2cd96c2b467af3b01feebe1e88e0de7bd6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XpXBs6rsyfRORuAPUwaT8yZGsXyz/F/Ws3L9NA9dS+ndVP7Ne3Tc5K3p9hW8Llqx8N7PxR2oD1Y/670rt7efCw==