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
- 6fe019dcd24f059a3ca911da6bc341f18f4db5bbd9c63aaaba62d3cab761d079
- request
- 18e7a9b1b0876036204f56f74ab91fa59e1ac8417c317344ec08f5756490720b
- transaction
- 399747f0b8f27c0d330e209981aa80aeef7723b6821fd9d72f60400186ca459dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 561
the chainentry 561
- sealed to the entry before
- e1c727ccb5f4111c4f16f7cdfcaf5b1954e14ca65c05a261af85deaff35a793b
- this leaf
- 911bc4a771b55eef12f324590b640ffb75e652e02f34a3ad7828b856f6d10df5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dYNfxnkbOl7zjeAntYG/S777f/nmkjLxF9/i0BXnfm0+qZY0KZqbuo4N+3zDFPjpPf6+iY7h2bkaELzZPoKTDw==