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
- 3db33ca631e50fc47863cc4830936080ddddf51dda1229a7aec0e6f450216c25
- request
- fef413cb20d0c914dcd900fd2e727df679c055cb4e83346639a67d70b877818d
- transaction
- b3c75971555aece44e11da28d9e75e9b60adb9d61d0f15315bcba8589f5eb835computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75580
the chainentry 75580
- sealed to the entry before
- ea215fbca1e279f5e3cfe2983595cc69a0d2f763489763308ba8b61bde3fb89d
- this leaf
- 87c1c092d67774c7d1b305a47a53da9709f7adedef007b779ce0db7b59ee7dff
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TB316sx93Ze9LDn5Ni9FCAkdmr5vrWA05GwTSoyLgacJcPXZas3kkmFbUw3abT8iZGq+iAWPJXPG5V1G59SaCA==