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
- c680693e85251b68478988cc7eb5aa188dd884be8a07ed3d7c0870f2de6d1cba
- request
- 59103a11514b62c3014ba6e47004b151c0d3fa4466924281fd219face3c425d5
- transaction
- 16c0914233b2fe540982b598fc376a55488845e35fde30698373a7dc18bbe4d3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37986
the chainentry 37986
- sealed to the entry before
- f9c1fa6823a62c15120a9ee2369d3ad23cd9464c9ad22004e3b0a4965d50abb8
- this leaf
- 641ff039acb803ca1cf5a4e5cc1e493463977853b32e235a8ddee1ca025991b5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zksBi/TPTPX2d0suSk2dibzi9NlbdAfouIXlFX9lkUI74hvxm0vbgT2tbFxTur4rjRGMaOUS0mzFwTpYDm99Cw==