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
- c23200071c26ca481e79fa322bd332f92cfa889a5efee93f519b57d96c949f47
- request
- be9d1065167bd81f2afdd987ffbae3201a4af6d5864293ca8cdbe4a1d1267db4
- transaction
- 0147a84efd38220372c75d8f08a48ed4586f94ec55fc918943c52a4ea9288f5ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22551
the chainentry 22551
- sealed to the entry before
- a8cfcd15ef7c6f22f5ed1dd65d5797407468a1df54d38505a6de8979739b3de0
- this leaf
- d41a329a8682a8fc6267e00b6931616858c5958c0dff8f5ba2ac57a1c1e9c458
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0J96Kntyvq/NwKcZ3nW1pfHdJplVj/R9Nt0NNF4WKp5KJMivBJgAduOdHuzHRuc7DCZM6RpHyLIJGVU1KdLXDA==