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
- 2c38fdf331128ec5e65fef432b3040c7b7e40257a09a903c2b57e71668e35630
- request
- 7d9bdc8e46ec41880839f021f1107da297b0be1e74a4a0dbf7b74b2e66693a38
- transaction
- b7f008897bc272ab168c06c978f2982a053a870d49761406db08496e46144940computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56833
the chainentry 56833
- sealed to the entry before
- 2e518a24689477aa78eb46125e335023c351b07b056b096d8dadd53112f63af2
- this leaf
- 6929071a2bcf5c12dc4c9bfc8f14f7fb7d800109d9e6a46ba54c2b1b32679c37
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OomM8i5EpPh6MuWGyKLuLepHjzc7uJzDCXm+HSOrUv000AkabmC3ACtZ/nbwc2xrvZdSszhf1DvCfOkpx13HDQ==