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
- 3e8a2e2b06755570c94ddd49d73717737b6238078380e3610ee2514ba6ecea52
- request
- 740b0a4c37ac759afa0088a7185ded28d2da61f66fd4635d3080ed96a145c37e
- transaction
- a3c646548f1fbb5b1a6f9bb2fb897259e97d82913e5f31aef578e8aab20decbfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51685
the chainentry 51685
- sealed to the entry before
- 2dcf609168fbee905c3ff574d0ccf7b6a983f94922774d675894da735a2454a1
- this leaf
- 37c619bfd46b5e744c6caae1de9b5660b4fd578b2fa670c8083c83604cba52c0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eYdU4n0vtzwgWWU/fCjK9fRbI234A7EJu3BGzWlm1VCOn5tiCxTSCG0yP9DCVI8h7iaDXS/limNacq35qgIKBg==