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
- f0a3264a06080cea0ec43de2f23928c5923a5eda48a0c739937a76aabbe46734
- request
- 89a0df0254731950c5d852d0f85fef446e4e43709693f91e5cdfc799c7a82db7
- transaction
- a404d76de4bf34daed46563c9b5c3c6249ab432f4e3223c20fea044c56597e58computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1580
the chainentry 1580
- sealed to the entry before
- 44636c3fef8e0cb73ddfb90d7d94345f78f3098b0e726017cf7e58c2b82b4e99
- this leaf
- 13d13eb5be4c7ff49d6efc17f9a2b664a031fb4e713e47fae798f0db19029013
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KWd55wV3eAReLiZft6SRDIYhvcDbALy4gOTxpZxsXME+0LcHDBWE4BLNrEpHd4CHjSrr32oBTIYiIRlaVeTyBQ==