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
- 0318f7fc03ebcd0a999d87bc6eb4f161fe1e87f2d401d84be383b37f7ddfc3f1
- request
- c43711132329d0a461b0a5fd29cab84ebfb3f8111dbed0fab31e5fce6eed013c
- transaction
- d5b3a731dfe63580989048815b5af10ca22b9ad3e7e2e83bd520134a6fdc252acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24223
the chainentry 24223
- sealed to the entry before
- e57e5e87f4c96abf9afd6ad1cae4e5c532b329cb2cba913ac4bcb0bce1fd7617
- this leaf
- eb0b4f248c8479bddc485e87fc6b30668dd56ca36686fc2611d2034842b94813
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NysrKUAye5Lh9qZnSBUMel/WsjJTb6533eICF0OiNn0kZzru1/bqD9OWg4S0n13P+DnuA445S5iC3cm7Pj3NDQ==