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
- 3b3fc3443654f10992e4f5d4d3ffbc4bcbb34b8ab979561e531f1074e271cc0e
- request
- 3a170ba69213c945c86989aab7d48ae8c1b7dccf8f254437d09e7106479a30d5
- transaction
- ed86b383e9c4120ade1f89998684dc97b3837e21db0839e61126536c2819e48dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53683
the chainentry 53683
- sealed to the entry before
- c46135bf6c5d99c5af801ae63a70351c512e6bb32ca413b248df23a53d8cc038
- this leaf
- d46dc04e17950bb8fb16cb124ef97c84189cdad3496b38b30ff585948b87f508
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dGFdFoq0fhKr8hQ0GQ7IRpB6d8IvCvll1dxFY95JUS8yomIsmlc+PJ/f6V5EcKydmrJpsLt/HGc9PSBhQV5vDw==