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
- c8dcf27f20b789c6556b49a88a3b3b2649fc1180ae0d3ee78611c2b18c086a5c
- request
- 9594b9551d6e2d010d5f33a492eb6b5ed76bb3c83fd41681f4dc99ebd992dd24
- transaction
- 5e10303cc809c273fd886859e0bdd64c30e7eab7b7f2d09c0f591c12e58cae70computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11456
the chainentry 11456
- sealed to the entry before
- 0e6b085b730a17e61e2e6805d01e9927b0bff09be4bdaa690a36b9a18a798ecb
- this leaf
- edb3b923cad00d856875cfdd10faf8527316028b3d5ebb7bf8746df0a03a3057
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FJr7b/FL4lJuwBo7sxCLw/MWU900Q4KLc41rCAKHCLRFu81HGv1S9qRBgOlH4MUZtKNk4wtyZE9Q5aBmc2qODA==