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
- 06b95851fa3b574d1275407b6915b667c1b7b9c33902391a744e2bbe253b924a
- request
- e9ec64468c998cc820ad9085b0373d609f8bb86904a3d544fed56161676692fd
- transaction
- 6a297138aafb05ba9919df440ae2b6921de4c0da0e6d1699f99407113f40dbe6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12052
the chainentry 12052
- sealed to the entry before
- f33632f36e833a50b8ed00f324382eb2ca21ce7c2278ed590883eb05a4557e83
- this leaf
- 24e7abc7ada48b6165fc5edcdbfb18abc5aca198c2acb91d98aaba0a0633819b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- X+v51Vb24DbiVc2Ta2z8mBrkwQWN7ZzIKctdKfRIW6uRIqaIKDJlhAZZ1IjlREpvFY1USbOwwWBq2emtfzHODA==