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
- 41bf89dd2d7ab3133949026fb404817da12d010170e74321fbbaab842ef47dc9
- request
- 50ffe25b5bbf405e31c7755d9bb20bc4b3a6ecc1594b768d3f4ffd70d639d35f
- transaction
- 4ad68cb85f189d3cd500b87527c8dab94ba45f8e914f80cafe30c45d70c00dd4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18803
the chainentry 18803
- sealed to the entry before
- 816b330584b39f90dad00004db7b6bd85b618405f82e9fd4b866c7775eb78c9c
- this leaf
- 3f9d0aa1c85b7e96487a3565f2bb5e42a162b0d1dc477f5619069bd5f68c670e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0GUpKlZ3yjXgzzsWVhO8V7G8SkiDFpHWgEq/vk0zuT7hDFJDP065XBvrrpiCebj72yD+50h/sJMHmHKVvsujAg==