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
- 43b4e437c2500a4b27aca8aa2567542d1109f8c4edb9e86571d7a60466d0a7f0
- request
- 4d6de9b6a8daa0707a5055376a863fb10431ff40691ead102673d4c6571dc90e
- transaction
- e3176020e87fd0613e51d1cc98f04c12ff7f3592485c8d57473059cf71eb020fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74094
the chainentry 74094
- sealed to the entry before
- be6f761160e1f218404cb635d60f73a80fd7b3cdcc88c84825192ab17cad273f
- this leaf
- c5d93fa9056141e0968a658c2c81d4adbe8a22a2013985947a91bd8f54b2cc60
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OIXbAKD/U/Mak6ftZ4FdC1ixTpMUCXExxIM3tDdmfsgStxwmN//IKpDOTTezH8jI+numIw5wE5C504Q7bpHnDw==