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
- a2e4a9fd1288c110ad3035948569c74ab3763116813ce4dd2925c1aced186332
- request
- a706ed84a76fcc1ad51b9b564f2b744fa0b1deb7ef6174c502dd8ae5a2cd105c
- transaction
- 65a6efaed0453378fcdaafa68921b058331670bb72b5460851f19f608d13b4c3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34218
the chainentry 34218
- sealed to the entry before
- 85e759883c55bfe339a362a0e475b0d228e43a326329676e6b9681594d9016dd
- this leaf
- 22bc66e9c457d7b91aa36655edd80980d17b39f4faa2c1cfbc6824afbedfabd1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- N+E2kB71onOpr5TiCycIOhqVeKWl2sfJ7/1a7t+YGYdTKnhZ8fQOSKYt0i7yoQ2cuc0yMFy4qESa7D0VabOADw==