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
- f7ac650bf655260ee75f81d1fb5a2e534405ad1070b13c9ef7a44a91520958d5
- request
- defc8549629f417c4479d26c2ca9a723417a29640622dad877b863c91807c653
- transaction
- 1447d9ac00e6601604d931291ee8face6e3578640f3b68b7961dce30f3bb9137computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58211
the chainentry 58211
- sealed to the entry before
- 850d63aaa8023fc499b89c41b263bd3a96223600c7381363f5e42458282b1235
- this leaf
- f365ceb1e3623879410458897584cfd00224affab13f41b375db201523bf1673
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9lTLvF5Vzh0cDv3/7bibbP7hxIdoDGrs2QePLuis0VGxBHSzvq76BH7aY1NkpQ04fCTFnf5R2PaO12qxzAGlCg==