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
- 92590af31f7c1cc3effd5a1be3da8b8e10d1ee68005e74a86184dbb46e2f11af
- request
- 6270d66cfb560898ded2c30391b13b6f87fd13ede620543f76d51f527735ea73
- transaction
- a925bef44a8f632a0c00b0e7b447bad35692753df0003863d08539789e771db7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15106
the chainentry 15106
- sealed to the entry before
- 7a31bccfa6d57b8265c28e0b1bec650143814d84d3dec1b40cbb4e58c75cb801
- this leaf
- 6f4513a562076ff9d4a7c7b1c6a6e7e343aa809f008d9582d1ca37b70012f930
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- afuMzX5Gu/dr+Co1D2Oy/L0wk3M6W2cpAsl8VGXZMG3MGSkEVe82HZVZ9YEaMChxhfl4O9mzFuRXytFPpANKBg==