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
- 6da41a84b325dcde002d1cdf54947f6c27c716847aa54c86d1709feea24b5b34
- request
- fbc9a2df5fc088c9b14aaf299264f60068104f5d0b47b6e9f1764d0246d88469
- transaction
- 9ba59941c440b1abee3363d05e6969d1af77ef885d558994d60433234b356000computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50541
the chainentry 50541
- sealed to the entry before
- 5150c60ac35fe44fbe657e486eebd001935e84dfec27eabd0676c13b77cc520a
- this leaf
- f653f84be14893c67b07925425bc15a7ad9e11e43db2fee39c559cfc2ad6eb02
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- miAbvUAUD3ySftWAn8uUgR1VD1s5QDLrLGyOxY0FlczXinIzlozZBWXMK4wmmF/EdiAosWvwe8l1vN469fZWDg==