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
- 9cd115bb6282acf86ae3f6f97a3afc601379fb5d3c772fd2df217678376948fd
- request
- 92ea05693bae5834e3cbc36e8f02b8c9ed3c8a80148a0145c3d5f1a887acdcd2
- transaction
- 06515be6108d23527fa9c26a3afa651ee5aa6938ebf6a5da0c12bcd15f475e4ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44328
the chainentry 44328
- sealed to the entry before
- 3aa432ebc72aecc1abf8fcab9c883b26b016b993aba4f74669e56d2772b47f61
- this leaf
- 73d36bca4244d4ea3535d80e802895f580a8a2609eb11e3278f852c1676d4e97
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1bwfUJAVE5bOoR//iuHvFy+eFuittdugcLYFKEJ5/J6MwbhU0A+RoEYEqy7U7Kq7SA+1eQKiUC8uDtWizLzmAQ==