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
- 32c9435030a119eb2fd0f3b46b913cd93dc3981168c7700c070d8d146d82bdb3
- request
- a353d0d013070b603f05390471f4fad7814056876918350669c270de144e2cc3
- transaction
- 451e4648bd7ed25127c7291ba51a4ada05941acdf04e231eb7b32c1c43179413computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60553
the chainentry 60553
- sealed to the entry before
- fd28e5a01e2143a7f2307beda15afd0584e93dd962287cfecc9e302d9f05c475
- this leaf
- 2d5c83641ba392f360e6fa8789780a11277a8190fd81650c1cb1515b6c74b697
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bdePhHTvi0O2nPJOVxLCxQ+/cyW9zEEqX48HEP0E0BuntOsdr35oVpcH7OjdKITr0lkqZZXye7ghyO6NDaEfBg==