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
- 153ec5cb476b1a4825d3be13c8fcae976f5b9c23adf8313bb88e8db56d86412c
- request
- 2f64bddaedd2f1e7d1a1e762760322c09b99953998cc72bf071105e9981e712d
- transaction
- ad48db95c6daa72b4d5c951f1951b635d7634c9e1db562090254f0097ca01159computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75439
the chainentry 75439
- sealed to the entry before
- 94e2dc67a056141632a9134500bc24f4149a3de66a0935b7184a9fe6d14611da
- this leaf
- a252f484d704fcdca4cc5aaf0f256ea2870097134f57c72124a5b0d5db1ed1ef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5N0XFJAh86VVp1A2uYud8+v6uS4sqNSsWmn3XL0EhrMTl53bCYB4LPvxRNZjMgHQo2F6VGmL5rHiBnyy9ikoDA==