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
- 599f12ba9575ab3b6e139bf8722b2000b18fcc0f19d367cc15392e494e733aff
- request
- 4c676657791138202b72eb6fcc23620d8775ab74efa733cbfdad3d880bb42817
- transaction
- 3e89ce4fdcb3ab82ac8b75926a5294e758c6f043dccab7d9caf571416833b64ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1280
the chainentry 1280
- sealed to the entry before
- d965794a8a2a7cb747a7f8f13ab28144f08041d34d701c5eda205c67f3b8a354
- this leaf
- a8f8c1a8a52a9fd5788d04b544b4dbcaa01f0f9c1e7caaf8a7c336f3284eba8c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TpXJBkzB4sDLV7OKho699KuCp2EZplMxpjGH1lhr4YsOrAsbw4YChT0eTnGgJQ15UZ8U7sCnptNJgDz8dDC6AA==