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
- 784e50d864fa2720fd2e45531d85b504ece0aa132c6dcbdeb6eba24537da2863
- request
- 72b212486b385da2b43c3427304e2510239c54fcee5cb1b32d68038bd172310f
- transaction
- e6f1d4f0e9520121335f1190a93c0998562dadd9742370bd168be1e8f22d01b3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72271
the chainentry 72271
- sealed to the entry before
- adee9e86d18f31b99f539243b85c56e5823cc996ea38f49bb51e217afbee6431
- this leaf
- d441cf430be1ff57ed0acd61bc06cb6d92ee5315add126b622d6e057d414e199
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- A5voiI93VKySYNAgHmhut7UvIak1Grm74jwrlJK1MMEK1OhtHW7531omeK/hQhe8RT5y25WcK8o8QYIkLAH+AQ==