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
- b9da416f81df9352577b20c09b0c6c44a90aaaf1319a4efde8723e03ad30612b
- request
- 0079c69b17dd3ab1618501310ec266c064bd05e0a1e94f436d1e27955787c68b
- transaction
- 77fde18dff53d58073d49bc1e6e090afc943a2d9e091b6a51b2c9b3b6d50ace8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27423
the chainentry 27423
- sealed to the entry before
- 535a68e9fd484a6e532b7efe9983d6e910fded58313484b4d9ae44fd1a16ce34
- this leaf
- 25628c55c8813f4923e875ea3c6c3f08267c0a188b130f43fdf6d7b07fef0e76
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0OGtuIepZsFqMM5UxHZXdGVKBLy8D6NkcSx5a34cQUnv161ah0puuo7+LoYCvKFQAyIxhH8nusHg5ZNZ8XtBBg==