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
- 1f6ed1841937c8a9514b7a873430877e9e2f3d85c8a82deb83d15efba0e77526
- request
- cbfe898fced3075b77a251f4dcefc891da5bb7bda7ff80f7783d9e9a217aa58a
- transaction
- 4ca86799fe12c7d98bf1cc7d5e41b6daa0076cbd793ba86a0e0fa0d8720bc576computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30840
the chainentry 30840
- sealed to the entry before
- 5e152f72c0fe61d49f9a62d59bf15953645b6d90bdae74208d6b9ff0e5ccbcb2
- this leaf
- 1ccab2f89cd920911010272e8c2717a7eb8d59ea0f49bf473cef2ed13daccfc4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- K9ekemhASUlewH1LNLu39gPKyMBnu52EPtWMQAWyyw020vWQ4KaKY1NXyXwTeuTjonwnejePr901qbVo6470Aw==