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
- d5c0550da2e2ad021bf1f3b14a90ae1f9aa916b1c50cac9b76def518c5c47e76
- request
- 6f7e28499c94ee21afd584bbae9fd25bc8e1fe04d8b4de6e0a9a528fa1cd0719
- transaction
- 4ad31d9d319606c5adc08dadbbc6fd3becfa8f8cfa917ef0671c8b1d2554ff67computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69705
the chainentry 69705
- sealed to the entry before
- 4a9c2f101751aa006fcd41fb1f92a8564bd8efca60e913382d0cebed67c9c0f2
- this leaf
- 1668bd163c1f2fcb0c0d410bd865eb5da610af3d4644cb269ee51dd78bb33e1d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- d2nEqgO+egri3TxK/XqyCaRp9N4YZ0khoHyEGfl7ML+7pSbOwR3NSTqW3vHmsaXyFndx8egg/D540ck+E+ExCA==