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
- 602d83efe3b90fe56f6e6d363ed5183f96c506f515d3610e3f4924988b8ab3a5
- request
- 60c6381537d307eebd8fa1562a32593ac585ca2a49865dcbd4585323c0874112
- transaction
- 6ac51932469ee02647195d6c728be74589264ef7fc3d75aa4850386aa3a2743acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62390
the chainentry 62390
- sealed to the entry before
- da04656e037d14ee07f0b90b7ebe6f00084050638d1be6b2f8074c861a140d4a
- this leaf
- f24c91cfc5c2b17b97809bf94d003b19c639a969c51d8786765ae7478e9827b6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5jot9E8zOF+/LLPKBNN/5pL3tHSUzVErP3O818iKh5pub6ZQPsBs4O3iFKBcPhWIg5m1p1weFxkF190Mad4rCg==