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
- 9c01314ce75c417a54092063d6edb7935f0644ffa1467c8b4956467bbd0888b5
- request
- 235ee80a1447b4ee2160b7788ac23b2f9359464927581d3ebce7fd863f554ecb
- transaction
- 1a16cce5606a4fc470aa90a649c8be59350f4f5914e9c74affe5575ae1c3ccf7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19509
the chainentry 19509
- sealed to the entry before
- 9e89bada5a3e9bb53ac654a2ea3e00bfa07b6f9304c00db47478709ac842fd09
- this leaf
- e29471bbc09129de9489745e4750e6523defe88031726bf2641117544c8ddde5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tdo664mPcc0Xic9B+fXM2O9FkRfWVUq9FaOzF/VlzCf7EFMO536M/8kqJox74S3PR6oDoibZiNTyjb5Um/OAAQ==