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
- f23d2064d08747f954ca0df412c3e9cb1723bed28b0691dbabe6c259d6498474
- request
- 3a9cce33480acead2cbb4c480df0d5bd8844da919b49b9b0da6246d316b568e3
- transaction
- 90e4e4d291ceb66acb3dc669f8093086d27bea35ab0204f2e84ca06c1b1f3ad6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67230
the chainentry 67230
- sealed to the entry before
- 6b7f4fdfbb82c96c8489d2b53283497e98c43192ebf4b78b499a9f3f97efda67
- this leaf
- 64a3301514de4fc204edd801f035e36791df9427623a528ecf23d04eeee6e350
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Kjo18Halx3l1M+7UEXN7ikODecXmWG/jYJEotf7SI1gcC2ZUcaLrTj/fXGw/SkX4OyWQdwhc7BKFcRtRG9qMBw==