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
- 39f40debbb377cac3713514cf14a9ff35a21dfd2ee798930e752a33b2a6702d6
- request
- c0502c80f396f3764fef48d576bcade21b2620702bb7786b9cc0d0d38e0ac84d
- transaction
- 83157216ef6001a9f0bf0a56d28fb3d7bdb62e47c1c8b127584a6230215aa499computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20376
the chainentry 20376
- sealed to the entry before
- f9bde64543858a07c46040a6610eabb41baf16642956a904244fe269dfe2846d
- this leaf
- 06a493c91a989d86cbaac43d8006223014ef02cab33fe618afff15196fd4d14a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- O54CtM6lhohLKW3X/SS4OzURHjV8+p3sRYisV+XMRLERw/CzMEIcRrlYGKH5B+yKmeb5MhNqlsKRo042AOsLCA==