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
- a153014c3f2932553e9f71d8b75143e78c0adc8796c907434eb14178fa2bfe62
- request
- f3a33b243879d94ee3003033f6b1e1db4e1bc988ce2979ef11ae12ecf380f5b2
- transaction
- 549b5435440d124ab82075badf8bd6777b7cd6681a4a60e6f80905f7a3dc8aeecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61047
the chainentry 61047
- sealed to the entry before
- 007fe786957e2abd06929af570bb637b82d5bb6450ca58ac9d0c78de4e928c9c
- this leaf
- cbe54a3ca53708b98d62072fd11f3d749dc6cbea72b7d5e8e78e3cc0b3b6aec6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zDGKIwLQTf4JVnQS4ovlYMzj2/hsYDo3TbxqVx3+B0DuOX6oYB9SgnJeVlkhd56OEgDjNWfo3tobAoAIunlJAQ==