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
- 87689cf6403cb5923c2875bdf175beb6f2ce349352948bbad00bbb295cc914db
- request
- 57b500c384135454c4166d967936aeeab0cf8c3514101505606e87895e15222c
- transaction
- e9c4580de3bbe842ce1124cbcc80d8a0e00a735876201cc018f6f4da8826b17ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67533
the chainentry 67533
- sealed to the entry before
- 50a2c35aa4e29e44cad43a6304f3497c63e938d5f2555114536990a3e161f3fb
- this leaf
- be4c8abb1b311ab61282e74970b20f6a1259c9a595bc3cdfbea0ed994c61843c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MspCRpgWPQLLYpyh4Eq9VnsZuYpsQ2vylN2TbCAvhmU+tKbrdsR4n6xhOw+/F54Og3nuLTngk5+7pP+MZBO7Cg==