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
- 48b0587b4cc74fc8010b49b86eee9523fbad2ef3b83e5c1a77883a9e084afc00
- request
- 26fb0a05c07ea66a829fcb2214ed59b2df590d29280a3815e5f37c7e42843b31
- transaction
- 1cdfed73343b7b17096c6982737a4f526537514c68ad1a564023d7b43854b188computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64180
the chainentry 64180
- sealed to the entry before
- 6b5db7850246f082c681a1d2f9bc9a21a4abbefdad56b088a11e20159e083a92
- this leaf
- 8b77d9bda8be248c053ef3fd5e1fe4afb0956298a175861a45f7140a1393a3ce
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- f5ZiGOQoe58/Wke1IXU1wR/Mg25+LdEQ12wD9AAdYWt5UWOn6v0+VuO/BG6ZVsYOT9ew/v3/7E8fH8bEk1dEBw==