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
- be4949c406d1ed525f18cc1aa20859f98ba175074c658506f09cdfb9870362e7
- request
- ab93c0025c11cc3b1ee6e0f801d7e43e26cfb8747b17e202efad93acab49c3a9
- transaction
- 0190366443f644c2c6ac05fa2a73613e478ec88a1104ea7031680ad65fb4409acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34422
the chainentry 34422
- sealed to the entry before
- 97a2f3b679eebf81baf6a2cfcf2afad0ea312ccc1e158e9ddbdf0e8f724c34b1
- this leaf
- 86910a4f71e7983933b7d2918a77e75dbd63f967ef2e29c7a9f2b1d5259984d8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- i/V6yDddsoI5B7YJaAQhK8w3zHEs2rmqNZmvsJn4qlZCRw9C0DKKkTJC7ga3W4Qd7hYE3MlCMfgbnOh1EkXYAA==