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
- b3b67a70dd332a1a34a2df35d5f858444703ff6e6a0dae16f41224a881cf37c5
- request
- 6a317a804868575bff9f8391b6d2bc4156e6e46c33ef45ba484aca778d17999d
- transaction
- e5adeed52911f39b255c8a7ff3c9a3c81ad05c1a463576b796da3c1cfda6b4b8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2390
the chainentry 2390
- sealed to the entry before
- 2d9e4e1b14ffe9c91daf5e71d292e1109230e530c857e626af2be8335fcdeabb
- this leaf
- cbef907493c7536cbe13e633a377aa07f18271ca17406ff6b4dd8a2019e18a3a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- X+Tb6Qh2lDMOSqw8C33nRwUp9l5z7lGIDqDj/mitjQeaXzezOCkvrtFxz70ua8Z1EzDKpLJo719gdITb5mWuAQ==