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
- 116c26a2fb9d3bf062bd7c22a047b416aa6682a01a0a436d3917bb121124d867
- request
- 172c50ed0a97b57f571f5e3d1c7b2b60a536e22569b3fe0e07fe65a6ba94cb76
- transaction
- 22071637941f8665f802cad3c22dd33723f6167716bf896f8e6e17183f4f6801computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40367
the chainentry 40367
- sealed to the entry before
- 05194b2b30f9d11e45ee823474e29d6d6bc976a8f5872740bacac1176a7a0768
- this leaf
- 1f159339d3643623f18f727062f17d592032a457ccde6059a2e55ef522c31121
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DhYl9UMU2YLKzzSmzL4RQKdm14Jd4ZAwJs9AXdGW1QGnkMxQxpHgwWFn8kFlm2zLdbLiphul3yG4NQzLfdZ3Ag==