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
- 3dae1277789e916a6f9d846b26da2e83bc9962b332dfef947ce91e7c4ade5d80
- request
- 5237e16314121bb698297b361ac5fed84314ed3637cf6d2282adc7171c2c5574
- transaction
- 2d7ef53d0cf2bbf184962f4f2aa7cc707e167b7282f4477e6671b0da8b6ea625computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75812
the chainentry 75812
- sealed to the entry before
- b5b2107cb4e719efe4e7d06a4c5924d1d46c87351a8bf36cfc9e405bcceab945
- this leaf
- ca7497bf23e9c03eac45b65d31b5bc66afa8e02d0886256e1ef8ec66385136c0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cojCmVDjIMDhbuPRMjfJLnRFAzg6x/UTj59H9sE5s/uUVVORokXGzKseiy3O9l6JSmHMPIbYiyFsArX8FOLgDQ==