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
- 7a0c7c91f398b5464147182da1ac86a6d225a1c5c2afee03ef1f1cbce3e6e557
- request
- 273819fe32d16923ebb13120c7fa539305c9174e07b8a517bfe5a76bf778d023
- transaction
- 68da766fa5b1090c4bb09c74c482beedcf5492d8570845160e8cf91e36b31403computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66267
the chainentry 66267
- sealed to the entry before
- 4e1d65d9715e27fb1b0f31ee9f4d1ca43cd909ecf997da08bc6001f6fa7d5cdc
- this leaf
- d44653fe3538813cdf22693fbc7b78c180e3a0ea48371c718ce696319b91daab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xM8nMdr42lIPns4N+I5KqtjAvxKXHoqFfxlGtG8t1jLA9lVOhGwrwsIyxs8ZEyVEgOEeDkGdH0Emb2MGBO88DA==