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
- 7ed61797cf69cd3e81abb90c71fa854d275344df2331dbd40a08cb6c59a441e8
- request
- 6e2d343874b7e0e2ff091136f6d20b8de20ee29052fabae190b24ca75e41cfe7
- transaction
- 5ec894b550c7e4494ca34c0fbb0dbc8256d4c6ba8287862dfa0124ef9cc0e4eacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 196
the chainentry 196
- sealed to the entry before
- 8f2f6bffe2806daf0bb1cd641a7d486f35d30087bacc05104b49e2a008b76934
- this leaf
- 8c4295dd6fada8a38614503a581f9c720f6579ae2ebb3bb6cb2554e039ad128e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HdtCKtTL8J4GKoFg05IsXpeJyHBiAUSAYuXCXh1ib8M3PGqMgt1hhAgCM5kvEUb4gHRVYX5AqkiIh+040EMJDA==