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
- 315a188371fbb868ecbc1b36afedcfca1c928236b27af4f820a75ff3adc76a4e
- request
- 0db37c366a3e5c5f41f9e002b6e03e13615950721bbd0d8a062f990b13685ced
- transaction
- c25f5b298faf0c73044d8833656e5794a6c9d231f03f9d9a907dd301276c58f2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75002
the chainentry 75002
- sealed to the entry before
- 8fa672636f5fb88b7d6ba4abe38a83e4064dc21e3bd1c99c3d362b398dc12a2b
- this leaf
- e7f5ea1b6515774fa30ef411a0d8fb9d9c47c5812f9f4da45afcc9028558876d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JiOi6OtTE8fi2bEoKPdjtJ4CUccQBnsr8pUXM9jYWKVy5ks8NnxdMbj8neP/XXFIhBBxoHzCI5+aKzbOgBJdCA==