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
- 642fc007bf26e2e8ad044d7d61750d0a5dc28fd686cb1e3a14ebf8a628863f19
- request
- c4d639ebc6b5f5b88feb783e2dcd3b8765b512ba8d17e3621015f6a9bf3353b3
- transaction
- 49d809d4d2c7a15399d55e2c27acee5254789d148f31b8d4d775991c2a3072bbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74723
the chainentry 74723
- sealed to the entry before
- 35a7aca9fa2fe12df54f119c5ebec9d1c1da7e3214a6515e1d5294226b5a7aa5
- this leaf
- f3c2f8403dbe0e2573964fad9f4bee57c7e0790283c6329b31c8bafc34834270
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- USI/fa8x+5i0KQRYC+GqFkC09IscQGcLhEVpyDcu7CWat+9dAnoKpmfZUBZlwutE3EP+P3PkRkRmF7OShzO7Ag==