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
- cd1a4f3fd1065525a55fcaefe2c4504939a8c8cddae7ad79f7a74c634a7ff81c
- request
- 53c5a0491fb9559ff7346997d74cdc1da4d837924b189ce56f94cae67414bd3d
- transaction
- 0094e9d6794c9cbb6086c6cc88bc8c6348c147509e0c1eaadae3eb9c60759634computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30430
the chainentry 30430
- sealed to the entry before
- 44bbb8045dca4eec62ae8ce06a55095fc75592575c00902b980375f7922e5ae3
- this leaf
- d7d23d799d2b5711b2285b4754c0c20dc0f1efb38d235fc0a98c56e98714b13c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cO5XCWAUdPYpk/acG6pJWHp53CpogD6ypnoAlbfDMhp2gjAle3nYa2Iyaste+ZlgpqbLwA+xL8GgalU5akr6Aw==