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
- 6bd6373f12635fcf33cdae5f99692bee56c87f98d925b95aecabb5786cc9ae27
- request
- 56ee863e41c780bfc012a669dc7239a5d5a3bb78eda2ce1754d4b8f00e125a87
- transaction
- 49dafffea94d4543e695ff66609269e43194fce33325fd85285464ab9998c402computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11645
the chainentry 11645
- sealed to the entry before
- 9b8977878704fd86cf553f41fe0c3cea4336ccc45f8f9efe325e83b46537978e
- this leaf
- 7b0f170a5c1bf5d0732b2f9479379b843fea02c6b35e7f20917baaa5d45fec52
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6h5LHyf7N9fUI/XQR5tXzmeWpsU4IdAaUELNen5+nFoiV+JgbZNyfU4TrGv/e1VqM5ZzHe4hF4NyuDUR0PFJBQ==