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
- 556e44f214ec7720f60ff1e80b7864ee6d45ba74d8722b424bc0876aebff1df2
- request
- 2ad583f5c6bd0512f7764c80ba70bee1912c4ec1b2765294248fa98ddabe5101
- transaction
- 17d00ab87b94384d6ca6a74ec1f225e89722fa6445c04ed78de37641996b49a8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1495
the chainentry 1495
- sealed to the entry before
- 5a9e3a7b668a69f88d5eb9fe6a3fe88ffad10de3cecb6318873a823ef8b6b0c0
- this leaf
- 38a7db6475c1906fe404806e2b5e821b657990f52993cabfeb48053c549171e9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rbPXY/K3EGBvbdjEerslSGHKyG13gRnNkTIM3+fewjJfqXI1KOkL+u6J/V4Il89npH429Nnnp1sHFG0hE8fcCA==