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
- d5370b9d1128416af94453b689e483d0396127480767b1cd6b0ed50989e02819
- request
- a194b2cf79bf7707aba9507666a9ca8918daabcc8c505805329f6bb5bd1ea1b7
- transaction
- fdde25e886f58e9928e094754e09cf4bc1faefff0eaa6180fbeabeefba4b507acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63559
the chainentry 63559
- sealed to the entry before
- 448d543dd8e9f112eb1ec9cd47b798aac90da09596e60292e8c18fe744767a39
- this leaf
- 0c3dc5a916039fbba04f378ae49e2f894df79f44a20fb90cf9e2c35796f669d9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DGwBOriksc7wDAxO8rWOdDLpjRvltNkIX00E+7SiX0xogdREy452JI3mC3yYNTpNMGEy0vUgsfHko2AxYjsiCA==