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
- 67bfed7a8be826e4999c20e2e56cb4a1f47552742291becf6f8c051219fcadb5
- request
- d685b9501a421511d9dbade1fb9f9644dd2b0484b91e870ef42e9c9e9d4785ca
- transaction
- b76ef5387bfbe44adb9419902de9beef36dbe8113deda02ec5c39093b2996ba9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1700
the chainentry 1700
- sealed to the entry before
- 24ec2cc0fb9eec528e3a9ceb301300019a84488dcbe127d494bab85dffa54457
- this leaf
- e659b6cb4763dbf3d9cdc8aa547e2f2b9eb1251c456d92b8802cbf9425ea07f9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9ZGb8rTcQvY1azEDvvSj2a+JTWmja7wVNTIqy4XU9mJD6FR7zUG/gXMQ2l/6wNzWhCa/0+0HedK9+qpG7jUlDg==