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
- 35d4d4bfd69e3671cd459638b803bf399f102cdbeb7e62e7c31edd4cded4ca87
- request
- 5c26b7f83f055f0ec9892ca2e43c945889914ffd257dc85ac9f3d755d49a9704
- transaction
- 4fe40fa3cfbbe609a8cb6f520d47864a223656d6fffb6053ff0f92f570efb186computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30349
the chainentry 30349
- sealed to the entry before
- 1231832951df47f092b96a25eea596e1deaf9b3d15ad0159e5d47cc4f6d4f568
- this leaf
- da77fb52f1cbfc0c7a1e65415bf9c96b0e7223bbfa56c1be3927d94941819187
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FBMyRxP0LjiWso3N/zqSrHbHc2XPis29noGhTIEVnyHtPuAT/5XQvkLPLjB1uyUFWQltZBWU6OfV6Rx0XrzICA==