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
- 4b9118886bfa6122b058acbda1fa11db4e5ec70d9e878580dc18aeaa6a2a5200
- request
- 5ac8e3e4102784d629569d69cd2228dee065e6a8cb92fb9dbfe41a6356beff7d
- transaction
- ab2d65fe10d6df82bad71d1d0bb773811e44e025938082dbd90542616ebe8f08computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56619
the chainentry 56619
- sealed to the entry before
- 099b829efca252db06b6446535a8e0f9fc718abf4cd1aed5078cdd1fd5e78946
- this leaf
- b4ca7b01d5db3064f7b04f47ed1d6f91b9512daec55a06166ac52fe0ef9ce0c5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lSDpi+s5Ns9amSwMP52aDlLs8aTeXc8KHJG3HgCW/9s+UoYVwdTL+Re0nE+nbI1bHE7kCVyBXlqjtru/5CMaDQ==