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
- 324177cc6bc54cb94affee82c937bf0834d763ef63f4b7dd9bcab5e882cd3221
- request
- 1809655c54cc9768b6032c69580799afc6001817a9082cfd6004e925cc06020b
- transaction
- 02fb1bae65d40de35d0de02e5bd60e9283c60c60ab1a4c8e8de89371805979b4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62201
the chainentry 62201
- sealed to the entry before
- 35efd84997a50b14c1c6b7ae8d6e4f5b81377be64241e03a9461b678a958ce3e
- this leaf
- 6ffbe72b328fefe8cccb4e0e006b1390f2d3ff2683357db4bee4828b1743a30d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- y7tnWKcoeFtC0rfIhFkaA2QqUjgU8GBU9a7OvHWhDlOLnsVe/TEDQLtbqQkJ+V57n7MhjOAXqn1+O9CPUkJVAw==