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
- 37dc6cd91da0acff39abfaac6c986143824806e6444404c7b1f68a264fd74396
- request
- 1a62c40cc428bac63fe274669fd390fa2010965991428503671b84a153d5fedf
- transaction
- a0e345bf059e05700abe8d078f259a4e5b3d038bdfae555c3a05634fc316ac4bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74239
the chainentry 74239
- sealed to the entry before
- d13028ec1e89a2889a2ec563c71b239433291b1c9f58cbfee04f7430073db3c8
- this leaf
- 641203888d7a93bb8160b59d1a5a5dc0fbfbbedfc8eeb6772862fdc3104f3ec6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9xotjvylg2ilbzNp90eBzt+wd3NZ+JEaQo0bJMPHLY1QgDG1UYCSoWwoPc4Nqz3UajLsZPZiFAXAEI4qP3dFAg==