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
- 8b12a68c9f4d058af584142be702feedd4ff775d32eabd7586a05aaf4c763d12
- request
- 0450b1bfb154ab44df67fa7ed67fae882c0bdfc5d42a6559081c901f448a1028
- transaction
- 974952cd6129e407f13b61d9b323b5fa458cec76369a51c848aa1cfb7c71da08computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37744
the chainentry 37744
- sealed to the entry before
- 0be638ec073dcbfd974ffafac86f2b7660a822068a601e4ab371153a0b001420
- this leaf
- b9c30763cab127a60abfca48cb54e2246677a83ff8fd64f2c2d87602bd691aaa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /lJ71s3rV7IB8IFKuIjrRQmOeEkJBMdctK378ixjuQserqxNGNO3Ttp0iBT39CgVSCMkb7X8yYTysj4k9MrtCg==