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
- 9242aaeb44a6f37edadbc71a27c3108c651e24aea58b93abab2d34a29b99d52f
- request
- 9fc79879f252da51b7aa0384f91afdf02d8f05946c0ed977e0de3746602e3637
- transaction
- eda56341d3f49ef21ec05a9947d30aff80a8a2993ea769c99b8ebaa343f63bc9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8356
the chainentry 8356
- sealed to the entry before
- 5f507292480bcef398d229707448aa5187f5a8fbb5d6e385e6f78ba410608670
- this leaf
- f0270d7dd8fb74a3836a903b4732a15c41a070aa89e72d6be58e994d18e363cb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QS3/xudBmMrKBSWOrL+Mz0TeES/1aMjtduxtGsq1khNW0J+BAfdMga5IS+7Cd+VyQbKXcQMpwLERVNOJLGQRDg==