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
- 4c22cdb205997a14c09c787f4184bf860fef50a28548d03fcf7488c6c94fef52
- request
- 0f56ed4eed8357826edac2297faca016b405f1865fc28237fa944431f72453b3
- transaction
- c8b79c083a00f6a56cc613c496d6bf4e8ad5786e45d6de49595d0a9a7e3ce81dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25562
the chainentry 25562
- sealed to the entry before
- a31d528bfd2e7ee32fe9efd232f2ac252c37bbac25f71ed40f9321529cff6eee
- this leaf
- 0637d19c27815546677c62d771e031d802d4d07d49969f226e4e3041c1af128f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mQedfeavIIH/OHQ6aqk/oCWH5slYVM1H7UwbTUr9a0QdxlUmtLLE+74Z+AO0/Q04M1DehCuAN6SCpAVDRm2NBQ==