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
- 192b921f8594ec112b6ac1dd471b7b01d3bb22517555e12e84fe7ed2a672a7a0
- request
- 559ef18c2c5078c1777f75d412b5c4b7bf3152de8f20d8426d373d57631f8617
- transaction
- 9d1d25cc59a4be32d33043f0b66136279be99e1b1239f451b617287cfd3cd0a0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44144
the chainentry 44144
- sealed to the entry before
- 38e888d69613e54f35c2d85bb0cf748b6acccce8c435ac86b469ed3fc1b4576b
- this leaf
- 300f3acfb50bcd5d5b26a83e608a3dd64a55e7b55369809e212b0289f8dd82b3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L3clojirBJmVMj5+hA1M1NVnnlTEdjv57zn75z0eYu6qMoLeSBfBiaGyQBtZZkBrSDcxncRZw8Hfh3CGiuNLAw==