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
- 0f949909ebe16e5a58b20f87055218e2ce765260157531d9d06e3df913ba293e
- request
- fc019ba680b12e399698ce84ea7f25cf3d6729ff6a33808fe0951fd3487fa0e3
- transaction
- ef89187353dd2097db9516b59b1d16c159d49cb09a4ff707e896468dd070d5b3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42152
the chainentry 42152
- sealed to the entry before
- c686489fed5d740accc821191b3452d92244bd84521044b8e16ebd63d99d997d
- this leaf
- ca6b0e2683865449a270ac6177c90ecdd2288ef0ff19ac31e9cc1f84187b043a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BROxa9rCVIfgo0MA0Qe5IunjjMvqrJep49MxpTBg6AuoOKEDw4vlpwmtiZYNz2OcevfrdiStAJr9vpkfsgUrCg==