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
- 8b5abb492fd57b998d1cd61b6909e077cf6c41c1a7539502e840ee0d75bf3566
- request
- 1511d440663db60dc3ed247a4f859e0428800c0c1fbe74e36eea2d7e396ab998
- transaction
- a73f8042c109f1734ddfada2f9641b9c81015a719560c70e8577e7bc815a4490computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24085
the chainentry 24085
- sealed to the entry before
- a803a1cffa10ff016ba50d7683768feb38c64e83fb297e77ba6d8689032be97c
- this leaf
- c85931c37750f1cb287aecaa775903eec9e6245d0a1eb55b53c4e3411c8010df
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4hP2ZOmFQmOzaU1BsXHZkkmLtwYJEsJGzkCopVWbR2B+MdwES6A500/8udqSmUaA5t7d9kkz4cPAqZa23bXOBg==