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
- 8b1ff00c7a1c73e8a6df37f4ac7107ebda048a80a0975e362b1ec9ac3b20ef5a
- request
- b41f796815dc845ea2bcd9f4d01ed0ddb72063f20feb3feb5d11e2d0b8c1afc9
- transaction
- 43d538198e5314922340744c14b1eaf1d0df0e7b854bbace9f1867a641d4bdd7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20245
the chainentry 20245
- sealed to the entry before
- d2513616298bf1dfec19b54dbd063ef4f4e906a895730fb35d5b24e397801163
- this leaf
- 1abcd5b9a3720e2fb4b61238d243e9b74a447723b9b2572f3122e0ec90945ee9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XIsRKnUhddy6h4VQT3z1KxY7X52bwtyCAm0ayc8eNWayswF4dwTuv5qw2hFtcn1P17iryrBOyt+e/bB9l2FgCA==