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
- 726dd6457a63fcba0d78f5120c218964d354bc0a9531ccef97e1bdccd21d643d
- request
- 89d54bc08050e42debd01c3f0c5444040af4333361d6588cabc90d796e99bad3
- transaction
- 961c6c0e1b5d4e635b1e4188b9a5896f45a892b5c2cad070a072c2fa6b523225computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37603
the chainentry 37603
- sealed to the entry before
- 26cc2fd222a97320d3c8fa44b5dd41ce56f9c0e23d8e7caf42739d3482c887aa
- this leaf
- 52a96346d37bde8d21e4e899e734c2a0d3cb992374ee68417c6d0c066d2edeb0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 74tojATv936pD3ZLAHSLulEceVzBkQGLm1kDkdS5NpCiwhrHx7Yz7CTNnZp9K65L8t9HZgtf1GpL0XsirZUFBA==