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
- e50215312dda76483724e242008041693c651f43d3047c77b2d9bdc32a32c8bf
- request
- 08eac467f3718e05bc9f78fbaabef126cd6f075041da5558daf7c0fe08f1a7b7
- transaction
- c48c8dd3a7474b03b7137f288b754e9417d76951f0abd4d0fdb2e72ddb9f8ed1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29139
the chainentry 29139
- sealed to the entry before
- c756f0a14c6a4a3fa819190798255e9e0c73e951ac1e3998e2cf36942906bc05
- this leaf
- 6af184ebc57ce8f19c1b2a0341bd1447028bf4c2ec9b5a01ed0717a21240b55c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Eg2rPMizGDMKxY05Z+YDikFsQ5IAmJUOYwHjij+fQJnf+TZlT9p8MbrIR9CBB1x08DS95slG6+4nJq3+HUEdCg==