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
- bdf38f25b1f61508a257e8fb9e0200c661513e1fe9cf179e717b1252c8e755a0
- request
- b4b2f2f8d051b9aaa9d40950b41c6a196502d9f60f5f8431df534e625bb3f8b0
- transaction
- 4c0f94d0aa99c6a58bb2e358046a36de766fd00e09109aaf574ef1ebfe67e286computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57019
the chainentry 57019
- sealed to the entry before
- aeee2b1bb60a4f93e114b02c943a4fa87baf06d1d5377be3670145f7f952be6b
- this leaf
- e9bb41c96b01a72ff59985e61a11e3ecccf5236c5d390a20dd72824e47975ede
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- R3id045ca/sNIb591VuKAqDtDrxCHH/HH6yQ4NthuNzFkmDWt4aPV4aXR2TtgN5/kTRbAYBze0o5ANFoUR0rAA==