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
- b6241f77bf4c4253e14d5fa486a7e47c5452a3afa6564e991b8c68f2f226442d
- request
- 9d1b23317931d060f0db36d1bc1833b3b08f04cb0dc66db65132f8e72ac17274
- transaction
- 68c71b2785ad8e99cae240f5a1a4617c8ebb569a01716ffab586218a0d94f417computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1615
the chainentry 1615
- sealed to the entry before
- ac5d9fae064d601370b9129bb355cb6701307b5b63301bc79b21d1133a3d742f
- this leaf
- d5be4b615b5b2d776e923d319929072a24db0a6eb208136e8ddd7b15087fb262
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JGO4PaF3ER8734fWoFrbHEVhg54V51RKKuaSkf03xCmvaL+hyZ/dQz5meWyYOZsgpMMnQ80YrzSIzdc0rVurCQ==