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
- 823f0901aef578889d4dac97cf8ffb3bdc552d646e75f462eb5a0034cc756f2f
- request
- 3dab0e2d44f583b8accef8314f23621bcd23954c79ec9734b744f54fe9b00e55
- transaction
- 897619f2bb5a17e63bac64c476893078c3722f7ab28b7ad958ee1488cecfd8eccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49655
the chainentry 49655
- sealed to the entry before
- a9c39eccaa25ea6fe3b5dc57abdbfb8afe9246f78c0005a5c3155bbaf126cd60
- this leaf
- 32de50dd7dd631ea5f0ffc50f273cb164023b0caf5966d6570a51317f172b438
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yZiWT53aou0lYw5EbG3yrr0lifgxzh+hCbaYTSxcQA4iIP0n2oSkLWPL3Al05Bvf2t75P4S/Llfh3DRwbMO+CA==