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
- a993f7816499c4c4fe5a3353d7f65824df456d72c2b1b0f80de6371275bbf838
- request
- a2f58218be7c6662a65beb8e2b0460bc7d878b06130cddd01cfc2330381bd53a
- transaction
- 2863faff5da02e44717756ccbd3f69dcd096265605e8585f90b8b21df38fb13dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67235
the chainentry 67235
- sealed to the entry before
- bceb888cd4e8e44cc12e55240736eb8a965450330fa0a859be63cea14b0324fc
- this leaf
- e6b83b2cf90011d26ab46ed3a4c33705e87878cad3c12ecd05d92194ef4793f7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- g6tJDRgL47i7uhrxYi6SvBt+c9rGuX+TP++wLOmNoeWxng7TUbtDOKU2dpQhlSf36vKHh4WRmUUWJQhdYE0eCA==