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
- 1b24eabd70571314573330b95cc5550eb6ff4749d68b25ec1bff0c7545bbc1fa
- request
- 09979f95e0c542248dab74a48f580c5d29abd5e98bfa49a91d68b0bba6d0457e
- transaction
- 116849d87a44ea63cdf8bd508cbdef241650b9a7dcb97d76f392710a4c252acdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40026
the chainentry 40026
- sealed to the entry before
- 546dee3faf2c7efb7014d5dbb2b592d1b1e75813a80add6fd1b9cfcd81c8a321
- this leaf
- 81f764bbe0c372807ec131995d2376839cc930a982ff666e0b2f9c23b9ecedda
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- u9pjV/RP1XXJ6Eu0xpt4dbNPYmZWF33/wPa9Uc5lXqeM5GlQRJEaTT/pNKcRoGupkXWaowO/Z6ae2WFxvCSZCQ==