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
- b07f5392d04a101877ef39126837e409638369faac9ad6d573042bbb85909bd6
- request
- f697e8a91e1247d51b30ff91ef314d75708027efc55e1305a88d207e1c0277ce
- transaction
- 1a7cfa762bdb740ba57d2bb45032ee3ace8f8ae102b53b86235adec281ec4346computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61868
the chainentry 61868
- sealed to the entry before
- 124fe2bd631e5fcbec614181014f17aa5df5d930985eb17c57175d79bf3b9a47
- this leaf
- 552256af94b73ef7e2f9d14308894f69ccbcb302102a24b431ec4e46a3b26857
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RkM96j11n9huS17bDvMcL6ojEKrUcIKDj9q5rY091QHUq5PggI5OpWdhMYW+CuwaMKwL+cQE1YAeJ7It0t6vCw==