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
- fe023734caa596b4459148bda698493a4af15aab4d2b84e68c474faaf6ce524d
- request
- 67e3a3dbfa251ad9efa794076c540adbda99652051cada0c36b884c97e64aacf
- transaction
- 9758a797613c724c0ab83ab99dd5ff7caae6f7fa04d2324f2177843fd99f208bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11293
the chainentry 11293
- sealed to the entry before
- b1674841f8c19ec905956395fa6b424690f3538c9f845d015c66dfd3b580cb13
- this leaf
- 51ab354bcd0894d69beed1a1af167cde73de9665f85f95335e5c6fe0f045a7bd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vvakblmka4os+AxxHn3BybHDrDK0O3GdY+sIP68f2GP0jxRHdFm5p7dxnErYyuDgD0zVe43XCehIvHpZZiqHCA==