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
- 623f21e4096c74bc30fb91c4d9091daf909b53d4efc366e05216c5f2e6e5a36b
- request
- bbd89d740cb895819eeb76c5dbcccc19571b4217609eb83dc157c3d81760bd55
- transaction
- 95c280bfcf95427a78c7a5fba8a0519afbac25bc3d445bb116d0b1557c65f6d9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76355
the chainentry 76355
- sealed to the entry before
- 75fbc9dbeb4e6043438bfce27f9db9ed86d90a7ba9ca7dca2720a0dec44e9a6d
- this leaf
- 7885f2d5fdfc37438d890aca53407358900d7a2f29d5dc84a3a8a998fa8b93c3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 79jdfjku8mSgjAJuRLyzDAkfz7HUJuUNGV2eCyKz/tVf72xiQe56yWkjYnBS+/kygMkqNn9ZuABckLCBsz6/DQ==