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
- 76a1392a054dad236819c9e7e5a9ee5453785d5525ed402552b9bbf50071aa94
- request
- b4982aaabacb043a67813fb93d92bc6cc372086878ab0d2203e1eb448a9b1f71
- transaction
- b2f7fbf60ad92060629cff6738ec2b6f9a4d7d6a82937eabfa5f842e55cd0788computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45354
the chainentry 45354
- sealed to the entry before
- 5c6605068713a42777c4f137d9207308df30ccbe439efcd51975cce9f5c64d81
- this leaf
- bd56db6e5749e450e5dc55c10f534e9f78dd98e2207059698237002ed59b528d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mInjKybT+3ZcnHgsvARwwlC99uHfp6gLMEdgLy4pRj36X74vu9bkYG1UIBgHouz+dDNTF6C3nVoYjTNY2gMCCA==