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
- 691659b1e5fe2ae705b0e26017959ab8f14b80d2f0594d3293ea333048704a44
- request
- 4b955f23786358904dbd00a0e8f31f04b6d66bdda46ecdaaa292082646543f40
- transaction
- ebf9f0d8da0602039b34bdecec513bbf6eb420c1ee4a52d8dffd7fb8bc5d99aacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10872
the chainentry 10872
- sealed to the entry before
- 3946220a3665e88cea5203d42c0bcc1fe8a8b89e05e569a36e2e22cbd8166926
- this leaf
- 4e813289e33965237d527a399502297dd40fd1d7da3c86df1c9f79b77d8bf53f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3RageidBIe6cSGbT0kBtV2DEDyTmvBgAHLZuXAPnwEKjBGiCmrNbhdUd/eOJGMx0gsGq82X49iZnGHZIlEBPCw==