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
- 1b998718a0a4f7451fc19eb700cc91e618051dff97423f3a1f4738f0bb6c6c13
- request
- 3af0b48a89ef76040125431a4e78c9ba4c000e144c95bd89fb77f9688c003402
- transaction
- 569d4d03643cdfcdbfb97b6561999ba282fa05c4eaa1c59263d5655bda7c1113computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2525
the chainentry 2525
- sealed to the entry before
- d1c7b8debc4ad810b9459ff53efc9b3b33ed4dec67ba7075c00f6ac62a5fb859
- this leaf
- d840c8901b831238db0e1cd3e899a7ea360dbabb53cfa2b332efd614de30b193
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- E5jzzLRQ7wP2VhlE45ClkHu+Ahe1VxvC2qn7aqg+0LjP8LvrxzM6TbX9kLvXSU3duIguR5K0E5dPMvnnBzEEBg==