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
- e90d52e48c71d0eee4ca7959f55e449c0b8a650d246a09270820b8a6dd805178
- request
- c922531bc17a25b7cbd7773eca7b480a88eadadd3a574ceec4be9f0b86a15633
- transaction
- 48658af6857f7d9f48aff5fa24bc495678a1f6350e5633f57b603d4a4ef060c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71693
the chainentry 71693
- sealed to the entry before
- b8f06159ed1c8a7d246d3adf3825aca354fff4ab3aa59d397e3f3ff2736096a9
- this leaf
- 60caab2df42f526022cca5846d5477d4db8eb7532a03ec0c5c1c9f0aa84709bc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4WduNBI6oKSOB2Mt77WBSZvSnBZ3jL4gJFmVRT8hsodeSxiPz1KVXDsEHHM6pe1O5IIN+e8D5LMlJ6Ec1J5TCw==