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
- 540d78f4f798c53edac1e6e68c92cbb4dbe71d34983fd0446c18c2f7a609069a
- request
- c19e7862a2c20023ec412e354e1e01ef9967e4bcc8896be1bbf2e0cb8c5ab070
- transaction
- 555574a31cc8dccfd768d0b35e234a2406270106827525dcd72ee28c2274b19bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28199
the chainentry 28199
- sealed to the entry before
- 6f7a425aed93e495d4563c9b8f709fa0ac35c96833ba4c33e83541aeee40f646
- this leaf
- 32ba3432c2ed268da1a9cdde9d1db3f7245a5b1f48ce44ebb99ac907ebaa1472
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- V7VmGhusedBxKLkfesfvK9BJ0x/COnjVgk0NAe5j5nM3L8dj8KszU/AnxCSxNGujj3KZAmAo1BHG2BgHeuhgCA==