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
- 0d0afc16ef9442f725a7289441b5a0cae8dc9fb83d7becb8f7d49173ccc5de79
- request
- 4be0d984963b02dd78cace917ca2629de10412a68d27004ba07d0d803fc35360
- transaction
- ccc7369fbe70982aec213b15105b7fc0915097c5e11f9ddabbbfc00f65ca9924computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60536
the chainentry 60536
- sealed to the entry before
- 84eb6cb2c043dd86fcccfb543a4dbef1d600730109ae8b40def684796610a2cf
- this leaf
- 630a69ee7ec1e276b37c6130b4f3a020e6900b7e6e450b7e052e7563c35e94ab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +tITtJGB27Ilx8DbCKSjEXL9qmvKq7DExbqh2H1j3xKRN8Dej0Nhk7AoTZUY4FtrBv4RBWkkszih0askXWl2Bw==