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
- c3c117b65ea41ddb5890582d330c0132ba0ca7e221165bbb521923169828473e
- request
- d3abd06747475d9f12d3b130948098442c7492f7662f0e5c1f1ae2fe0457aee0
- transaction
- f2d3e53fe452e2f035002a486977e0e94ede51abfe6075dc60bc429415b4ea1acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12988
the chainentry 12988
- sealed to the entry before
- 93267c9f95a0b5fe90c3c9fb4669959c8b9127a4d7be280e8f18059cab69d08b
- this leaf
- 8dea3c317c44bb22555e4898cfa8f01c6dcb8b64bc02508c7352923642795ff8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /KULhVElmxOEslhjcKopwoKaSADWkCxEsKUGtsET3o4MyQqqt4gv6XrWzxJfGrDrEHXAHOfF6P4hvWRR1ZYXAw==