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
- 2ccf8dd7d745454cca21650ac26bcd22fcc3fcb421d6363b6e6a5c68e1d84192
- request
- aed0d11c3240e33db022842ab705ef2816dda45792ae05802eab819b790d75d7
- transaction
- 08ddc21b4f092620caa049e8d81523319b74d59b6974e92979e1fd801d3100a3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62571
the chainentry 62571
- sealed to the entry before
- 90c0fd735be9f37098fe3e388832699b8609f440b9a1873e582439019e549fe2
- this leaf
- 154cbe7dbd188f184988d5778328a84e0bb9198d3b0c388f0f8b85bd1e02688d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- O3UGGxsXV7CNVty4YacPHtSz/4vPJtO86vFDhKo37SR3t5QNQ4zEQtV2Od6he15c4U8EwZ/XBHpko7ddw/0wAw==