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
- dfadf57383ffb3ba2bb17c5a6ae6a4d4344f26bc894f9c6f2b612496eedbd3a3
- request
- 85e6458cdae9d5bad5cea26a8c68d34db9853ed5e656cd261989a6c831aebf19
- transaction
- 882a4063496ecd3cc8c2ddce5d1c8a4d4e86e4aa970c6113d4cfc1b9c4760ef0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20767
the chainentry 20767
- sealed to the entry before
- 441092f40188cb4ad775b8eb5feff7d8510aa2623b849fbf4bd161870b6d4d55
- this leaf
- 92932673d7491ea7018c75ed1942cbb5830aa7bfeaac692ff9063e99cdad2f82
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- I4kmbgHOanE10DGDwULBurwT0JYiIZvd27zqm8vzGWQDTUQgE0f302yAr7c/0/6VzzgnUU7jkOIbmV06srVZCA==