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
- 17006d85dadd9f218688292af29f8701c4d20dc4b764835bd754ef0e34264115
- request
- a62618be8eafafa71077a36748ed3b09a976f0cb1dc03fc713bc5039dfd4c4a8
- transaction
- be99e89ea31ad2529185db513c3938b497882ed657a00d47f38b6c148066a38bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20762
the chainentry 20762
- sealed to the entry before
- 208c5c9e7c97560c8defe421ef3cbf5ca545d5fd4734ff766a5c7107c991de28
- this leaf
- a2a4dee5d12fb9861e81d6f764438b23be6d730a35642782784304ce2542ef65
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lTCa7uhjOLokTW56m19ZXFXIVBP7GL1Rh7pfZyp2AcM2sHkwTlh2EJg+fRCzwVC61ScFzDKUBV4VfRZopNWNBA==