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
- f2f361c45cf162f508295d59dc238af6bffbb7352f3b181ef7c2a1ca821aeabb
- request
- 08876e3d6956b5803eecaad7ea745adfe5cc2a9dc56a7a7fcbfc874441038472
- transaction
- 510edb99c324a3ac49b69d66aba38341d264e90c0197505fe66f6b49bf935ce2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47060
the chainentry 47060
- sealed to the entry before
- ea48c4f6f4eec147369100853a36df4fd2c6dd95ea86e080459f633ea2db9634
- this leaf
- bbedeb50939bec123b8bd2c6504d314236f9cea20d024c7e2e0c3ccc76543baf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7MjJwUOnNPj/TvKp5clev/mb6EPCm/v5LyqESAv1ucx6IFChMDSZHPW0GOpcvnPRDil2WLASfPWljeyX2bGCCQ==