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
- d788af09c43ffc722fabe9414551ea2d0f0952a07a2479d106746c01f0692970
- request
- 2778f86452026a5a0cc0202ffb3d5a3404474ab71e603f10eab618ac727261c5
- transaction
- 39a286ab69242926fc74e311c12a6b49d3d5bcf0bd4d81d45c5c418dff7d4b71computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59946
the chainentry 59946
- sealed to the entry before
- 49e1279b4a95e3a3ac6b9058d01a427c6536be85c99a7a96baf2628c882a593c
- this leaf
- fa766f4c4875085544c6ccf01ff3a442d600810bf59e8415acf9eb5dcd3fc985
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PpGS8P3EEHNvzNlXzPrjDASDMIy/d+Mu1ob17dOUcM+dZe8+JOLr4/RhUTjcuhXXfYfFNOveGt4T/qrfCRqoDQ==