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
- 0ba9e89dc008ad7de4edc718d09834edac8cdd6faf5b984bc2908489f2bb905a
- request
- 53c64404e32cd200565b3e65e4a6e015f2e2fe9d5fdd9b8e5cce3bc99a71caf1
- transaction
- 5dccfd16ad61913ff7f2ece9e4230287e5645d773af72acd141180424400c76dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13938
the chainentry 13938
- sealed to the entry before
- 83051c23dd4a3ec0ed27e4bf96e010aaea2827ce61d1e64661979ddb4865b248
- this leaf
- 58b4c010e91e1c7ad5353613190aedcda6626b87aefb911839a7fa3592c58334
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oPXPPuzvsBOvd5qSHIMpkTGHDK70rN06TtgKLF57NWbWJuILGOZV0308NTBNueO7vlwBNJPf8FuCdYn0CMWwBA==