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
- ac1055323e4d603e5824e4aa2b25fbc019eef1b5e3cf5a7c1f3639f17e134d88
- request
- b5bf11a3a33f454c8a3a08d18d0e524de34cb0ecde98db287b2acc48e3a7e420
- transaction
- 4f2457d7a35bda2b769c27913a73afaf37826d42bd3d4a6c5386dedd51064972computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18008
the chainentry 18008
- sealed to the entry before
- ceba46f68b178da853d8ae47787d0cc475a3d50b6321368cf87ff351fb88a51d
- this leaf
- 21af5689a3498add3ca0c0edb207ef98714dadafc35bd5e2af87eec0c9177adb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fv5FO43hNBoMQfpMPUhu7GlSIFaLpE/xh9riL/Gjvo6OLCsyVqcfpXgS5j6Ypz2mLAAgGCRCQnY9dBswKSlHAg==