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
- 8452259775c3e42de8e9727f1682f170b75bd2dbb72e670576ccf31e5f32076d
- request
- e1a34ebdb5162c08905ff93f5ed668242929bd7f9e6aedcd5281aac7d538e22a
- transaction
- 6597374438e963deff366d037484581039a638c1cd5d0211281875e66dc4d408computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59467
the chainentry 59467
- sealed to the entry before
- 8386a4461dbe68a88eebac2c5c7ef4674d7af2c1e09a622431d5862faaf5f5e8
- this leaf
- 296ab7234e6673a4e136b4c3b9b14f88c451cc96485d3c9d28f199d1501a9345
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0VipLsaH8f7Y2HrBLcwS44azCnnFUTBirZrAEIQvWhHtxlAy9Qsohx7f+bPWeAQjHWCqeyrHGtuVNzf/s3x9CA==