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
- 30c18e80f5b8042af599944fef5a6b05a14e17fe520d54f8dc8c25150e27dab7
- request
- 2f1ef638123881cb15d7f2f3869b598c55bd40ee66a456db0409c81695e9d97f
- transaction
- 637c77e23bf68d9033109f87d7bf591f8d9baf0309db49a1b4ac1061c8c7ab4fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8765
the chainentry 8765
- sealed to the entry before
- bb8dc064ead752d59cec1b72d1c91a22e0612e42258d01d2ee00f5aee3af73ab
- this leaf
- 1ed3b54ba2b1d214322d1d5537e9c84932e1fa5580a63d3c5d833cf04de4c25e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WOedGuW7x5FD4FyLrG9EHOnNWkrBO2ZyzmQvXQ5tRBJNWjODiYxqrskG6PdsHo+iYD1vVLsbO+7djCJvaN41BQ==