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
- 6620595f943e316bdc248c2244852612f2186bd4b9ec6cd3d46104131d501440
- request
- 3bfc020a8103f43d5e6b74e2fc4702d90ba69bcb49f734bc21705568bca9bf90
- transaction
- d35dbe73a07bfece1f56f9b970e24036fa5b14f153c1a307fa212c29200e0177computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64460
the chainentry 64460
- sealed to the entry before
- c20426d6bf628c3818f5397b75ac01bc9f8c29ed6470f07df782b619ddb2527f
- this leaf
- 95ddc6a708eb3a94b3948840f27853b61894e9c33b78becd9ce02ff4876a983b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- l6PYohEKC/Wo9vD45ytHMdg9ryt05RWOHny885if1/k1I5uPtM6jh+NinPyeHsHbhO2lIOgSURmi9qNpyQXrCw==