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
- ad040331938cc407a5ce5e684139f161bee22e5bb8ec5cc9251d855dc798a85b
- request
- d7bb6f44a05ac7e0d8a3f6b2b3c967663a8393d0fb07ae947900f0a62d967331
- transaction
- 01ddfb5936d8a4cb6571a02c06830c3ce794d583066872d0653581835aabdea7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18333
the chainentry 18333
- sealed to the entry before
- 54dbcc63f630c3413c29443e410ef8378be25c6a06d832bd2bb2023267367a46
- this leaf
- 0de6101eb2bb6bb8426db712fc2dd7f61ab5c82eb0a68f897fca262bac8b2898
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 876wuy0NXOkrrK56eVuh1KwqNVDj06gQICb7ee7uKBXL82VLO+4wHNkwmGybTcrWo28yOT/JJdYgxMTrLJjsCQ==