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
- c4654fdc506700e7c3cddbf3eab01a4e612d45bbedebbca1a3f84450b616ba71
- request
- b79132708fe06c5cf0ff8e864161945955e86e5647fba0fbf2f9ffad71251ada
- transaction
- 5ca4ae7ef422078f4cc3c0b25bb8cbc9b52f8665bd92a1bc24bf0320e4fc2b74computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66089
the chainentry 66089
- sealed to the entry before
- ed59ba315c8aef33e43f30da9fd9e63fa24fd17b3359830516eb84f9553c6354
- this leaf
- e61a989ed97121b6ea3ba383f19e57d3ff4a9826d3dde68e93cc1bf748cd7866
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EL+1QGV7Xxb/Xg8RFO0aNZlSfnsXOZB6mHv/uM+QqvJhfBexXoP2JONdaO+WtOEyJgE/XuA6Ev/eYuDEoKbgCg==