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
- 177a30494ad6272962830c059ecdf617f2dacd61b488f39d479219af0a2697a8
- request
- 0c03b632d2a9f8ecac6360d2c0b152d40ebbef80138171f46ad678e6e98454f8
- transaction
- 031e04a2192e95087248d8b6788e5a730cb38e7fd30ad9d47b1c2e7d24bc1086computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53248
the chainentry 53248
- sealed to the entry before
- b46ba92c1a7ee83bcc174841673b6d7c8f7e5751c025f75a27ff105def7df531
- this leaf
- bf5e95b2cbff6d5cedafb82f984d06f6e0d11ce9eecd13c44d72e2274a30c2fd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b6giu2OFgdzejTGs802s38bV26j8dH6VA1SNaLCz5CfSe9b+/S2LWuAsP3Sp8M8qD+h90v8XZd0++UT6fpd8BQ==