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
- fa59b6a0802b01aa59c70ac7cb1a290d4df0432423f82a99c4e5718e099d60df
- request
- 6ce0adecad48465a06eb0aa4f5471d0ccb9d0cf9024623fcff53f57d35112325
- transaction
- 58ee42c79290183ae51c8474d93c92acd5dee61b1fa50087ba5826f77dd2a661computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65218
the chainentry 65218
- sealed to the entry before
- 041a7a7d0d13cd9d121c80ded6f0dfdcbe79153a6752e2798a09a2102e106939
- this leaf
- 9f06030d19009f85b2ef82fdc3c90760c60d23b3e7b9996662de87f4946ee8ed
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- T5Xgv2dLnd6wKLeFcKoilbY3WFskihHtDO8xDpsbl1D346Cev8YKhZwCQC68w/rm9sFI0FaOM/EZBazv5BoqDw==