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
- 9830f42b98486d6e4e17c743d2189fa1a30a3e99ae7a59b11a0646c643ffa7a9
- request
- 61f4447179f1c8d70ec204b2ee08596e885fe65b0b6eafbdcc3240787fe1cf81
- transaction
- 7e2ba338368d776fdd3ce007edc5cc3e99be4eb7858ac6c5fe3e749fabbee386computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4427
the chainentry 4427
- sealed to the entry before
- 478c80a0427d572bc1cec6861b095f1ac2263bd2aa1ba631769c9f7790c8828f
- this leaf
- dbdc48c94931604b1e5d7b4469ef4074dc7536665f0b40a6be30c45abd3e160d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mu/kkwKZK7UIOJDC75uqlsEDDAR7mzeATMdIYvz8cZuKAeGoatcluu2nzj4rJO0h7QsZXnWE6uHFkIzSUjqtBg==