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
- 108548268c9e294363eaaea8ef82e3edbdf980a0c24e5fe1c8cbf5d194e45279
- request
- 6453670a30c569f3e52173d5ddeb7b30be262cf9ecb3fa201d666927a9f24ec2
- transaction
- 5c91ef7ee76d451b02195bba42341ced34118f51590ba987c7b4a5360927f14ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17690
the chainentry 17690
- sealed to the entry before
- 2f38be295f4538f24611076339ae032c240cc1d8df5d722e4cbf4e871fb008e4
- this leaf
- 566032f9a45941be4464fb2ecfd76d05b429ffaadd74c4bba5ffa59d71ddc6c7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iNr6wuxgRP5O1uUCDytL4DYzLnGCpi7tCo1FdWid1JTFS029IiqFrj7RMAOY555SyDkcPvWrB04eGHorEnATAA==