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
- c7455ae4c694407cf59a8e160a9b342fac34813583b1d341517bdb127313dae6
- request
- 460e45ab970c42678086ca053d067dbd7f05ca0df004a5203431f23df2bd7ff5
- transaction
- 00f8d3b95c0fca837e61962ce3336ff6ef2c0e0c9cecb9a3860ff6ba260f7303computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 731
the chainentry 731
- sealed to the entry before
- 02ca82541e0096a3cfd15acdc87bfd8f40c8c21f0a92a35337863280a9e3396a
- this leaf
- bad81215871ed4ff43bb496df74ac180b9efe32fb609829c69149f1fd554f19d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HAzwIhd3sRib/Vdg/31/UkLHow1X7PKWKz/1R04KmXmFF8GSdDYlPF0+6XYCI777xr1gNA4b90H9B9Dn9JM0Ag==