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
- add5643208a470608688b9e1116657343746900e851632a12733f1bbcc255b06
- request
- 6f1443ef5338f2bbbc292434824e0a5048d1cf7d5a8bcec9a6f021c1d0881cca
- transaction
- e1e650716e4848994fe345ff87d5784fa6cb6df6794937fd124d5daa4e76f8d5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63880
the chainentry 63880
- sealed to the entry before
- 2f804d8237fde3feefb91a33b64edc4397b193bb67155d6c292dda734f997112
- this leaf
- e671fbbfd69bd75f550fea4eb84aff65d1f6d396220ee0cf8d42a8b6df2105ef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uNO6acAXbbn2LHu1Exb7xM225pIfm9D6oZYQG6mY/cqSTm6OlQjzfMYNvfl5WUSHxh2co1HomlF/KlAq9S7gDg==