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
- 5200dafff2a85f92660d848f73b9247250b9786fcd61189527d59fe8ac02b090
- request
- 5a9f0e0e3a05ff787f84a2e1539a1f187d1f6a29c4eb0f5307a2e938c359230d
- transaction
- 8c7da8eb2333e40e60b5d073f51134b12c997a86a9385c72709d006523e30bf6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46113
the chainentry 46113
- sealed to the entry before
- 6bacc638487bf76e6420ba0751f5d6edc4287c0a650e1839a7b9458c6aaedda1
- this leaf
- a0571b82e5fe2ea24daac6fc179664cfd224b485bc1f80cef1665b65b82e472f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- t4mvRtaGYe8JQSZt0c6fAc16KwBV/nEvQN3kL2ZK2EJXTsoqbSNR7XptvujoUy8mHqNncjup1rSP7A41DILYBg==