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
- b84b0d6796a42b2a23bddbeb652e9b6ef643ec6c705eb27597782ff2bccf24c9
- request
- 5057237b83de74ae1bb1434d0235212462a22c37df720ade1b666bc1dde2d009
- transaction
- f8627420468e2d0cf042762f1130af5907799d258e96b7cf3914f52ef8d87f22computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30113
the chainentry 30113
- sealed to the entry before
- 5f5f476bf992d7f39bb5489db04892fd11b25010e835c797a3517a991c9816e1
- this leaf
- a7d4386265552b833e097cc857bd51a7554abdfa629cd34540b91353a7c0997a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pGZNteJyqlKuEXelb3ildNMQV5hfRfFxYlEANlB4Q2yKVkG/ifQHNBuBpeNQjEMd55sOk28mQDn/VEQnGYtTBQ==