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
- 89330a6198344f9ee3c3024e1d2b7183e03b90c7134674084084336be951cdbf
- request
- f8ea236289689f1caceb0963dfe8bcdc424af397cf33a76a2f11645df4980c6b
- transaction
- 39a070f45d2365bab54840f19ebfa15cab203007518e53b2d4c5a854c49dba2ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5732
the chainentry 5732
- sealed to the entry before
- 88ae54417f9640d86ee81fd3deee42f9d489cf04273f107d4f34b8ac0090cd7e
- this leaf
- eb9c8e5e705ff215c0beb3060b7dc28c047ebb6a024629631e7a61aa7bb64e4b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3qVVkRcnMmkrncloNuRtu1KozOKgabu3vLDl6wkTeWCuzfADHsxQlL46cgNSdqP7rE69h5Kmi2mkD4urleYBCw==