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
- c21a668fb5b021120712c1959401e0019ef0d4e7f48b3c41885af08eec884490
- request
- 7bca26516a7f6b1049342df72ba3b63607468708a18d06a601e03f0e590948b3
- transaction
- f8143692c8f8228e593be01655f4bb12e2dc5ba408b38234e5e763c4a0a6dd4ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61119
the chainentry 61119
- sealed to the entry before
- 9ab13ce58a7e5f39ec806afacc8080ee73b3bf3ba97c819dd9ecdd33fffa4344
- this leaf
- 6cb00c6812689863fc721d0bca8000bf52ec5ddb0494d6c09a6b3a7c56eecc78
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Y/RTkpQjB4nN62FVGV58KKCcV4+XY38vX8MAU+pmYVqkuw636j9ihlx5/O2Aj7uq6db5yge6qD/VSFgNZQUTDA==