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
- 0047ebf6828fa440003eccb30cd117c3da3c793fff9bcdd8a6a15c59497ea2e4
- request
- 4c023cb4523b18b5495f412ecfbd6cf497df1476a880ab1c02fd1a8155b8cbe2
- transaction
- 6b26186519413d0b8c55b28f25ce26c89531be50e98b0e7a948749d549fdaae6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22164
the chainentry 22164
- sealed to the entry before
- c69353261520ab0eeaacd9a9dc045ea486870d27a1426fa8ec9c753cb985946d
- this leaf
- c42b1aaf48c9422e40e63f3770aacc225190df27fcde73474989d035ebf28d40
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tw+zFG/azoQ1enar0fqAYAZ1PiUfVXec6k9EcAJ0+VFzGFuN8K4Ar1mbA5T4/6ME1Lh2ViPh7dVAeEObkHB9Dw==