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
- 0b9362cf33f9c89679cd0cdf06a50287aa8781ff083ba2418dcfb333842f7d57
- request
- 4d225b99e2038d445f243000295dfe0c1059cec8d5703aa2635682cd53207265
- transaction
- 098f617967f9a408f46b7aed03e1eb260cafb2fa675b9704699ab5b5006125d6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12929
the chainentry 12929
- sealed to the entry before
- 99e31ab21be265dd7fb7ce52d3330cd4e0407a6d0a53b406f8e462c4fdc1ae5d
- this leaf
- 7242616c5ac7635f6cba7eb9283f3ba0695510096f534d201ef26c6713eed93c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- P/IoTG4MkZlr2LozPKjbybh6hvhVdlFNUf5n0h9TIMn1HOy3e4EnMbmzFITFOG18oh77nGi3cjY6ky7mioEaAg==