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
- a96640cc98516f87349426c7d174da8da5f88f7fb01dabf1f6f39acfafad57b7
- request
- 92ca1a2b76222ce9226d3516917a7a8c43c8acc70216f2f78fd96ac473b453cc
- transaction
- a84be3231edd33604ea57a969c890c502ea823e7f34fb3ea0c3de479a4fc68c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29038
the chainentry 29038
- sealed to the entry before
- abdcad446f449ea88c1d7f605e106a1a36b0e752f53c91506ae4b32a5f3db7a3
- this leaf
- baf9baa97ba14ab132469ac0fba252bef7bcba23624b594eae28fc7fd9f0d8ea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tkXMIuOyNdxmKNrQitxnitTDOemPt/8KkZ2KA2mqd1zHUteliXm5J9hzVf5ZMukOWzinuZJe6xH6X9fHXdo0AQ==