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
- aeb025db02b28c21e0851766a7dd45e372b5e3d06df9e075fc3e0707f6794304
- request
- 7b96f6350fb2cafed95be57fb2759185f5c045fff654d70915166bcefb6297c2
- transaction
- 40016e6dbfafa6099e2d4198a8a6247f70e3911b838a1a100152498a4752505fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1310
the chainentry 1310
- sealed to the entry before
- 39fe1241545835257df365c271aa55e516c6a666b9e07532e1ad2c1c8ed741d1
- this leaf
- 49cbab8326e3501117016d40e68845edfc73471ad8e3b559f27818b2ab096aec
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MxBukQQgRavLTdqHGu7hjcXpCmr+VeOvpr9yZj9+RjuqKCUargKVA4xCgX6E2dWshNTW3pK8n+r5CQAzrRzXDQ==