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
- ed6ebd89bafcdab2c23401cc82c59f8a174db0a004dafad60405c4619757da71
- request
- fd667c0f36cd09a2a783e66db6cfc784426a533ca8fdc01fc2e0ea16146c47f6
- transaction
- 98b45632d971bf7a51690769f6ec82e2938c4a11a94f646ea72712695ba1c062computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75476
the chainentry 75476
- sealed to the entry before
- ac60fb2d7bcf5def9070b3157358d0d27a5b830a6da37454b23c3d1066c11afc
- this leaf
- dd57d01d3b2e66cda60469cfad79b8d0469bc69dc668e48f79fb32a508b5fdf4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Mg5ey4u3GBOckukZO2DbULsyrEL4k3KxsKGy9wCKKQ4m8Ea7nM7JZveOE+K6KhgmEV1qQHakNF80qN/+pCOXBg==