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
- 4e0f20f916b144a237cce90dd31cc6dff47a2583f6d538c651f4e0e3805efbae
- request
- 11f045e6d2e39707f9f5688717bcf80f187bfc9f7db168ad5bc15de5aff67b68
- transaction
- 879f3d1f2624bc1c37296f8d7a4a84e879d36fc9f26699d26b1a43575f1fa06acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12435
the chainentry 12435
- sealed to the entry before
- 48f915fd4964c8c63d3c734494e5b64840c0886aed0615bd03e142881d5f286f
- this leaf
- 562503187a41801480c339332dc671746f8d6cb729fee5770548b93dfa69cdce
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bxEDxUQMUPY96EbXBoUr3+I86/FTUJ7TnZaAcIiMO39j4vZlIR7Ui9EhK9dCpDawXfGE2iXErYUYCynFcXdNAg==