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
- 23ebfaef86a8c410e4751b90b06cdd357de40bff15535b05a16735f0819b24cd
- request
- dbfdde782608d69cd4ebc3eb401e7b2fcbb9bd1e42ace530f86cfd2d73c2e35b
- transaction
- b186a8811cfbe0f6b917c677e93f1041011320d2152aad1cc1f553c3bc5898bfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10915
the chainentry 10915
- sealed to the entry before
- 251c44147c0d9999cfab1cea395068a86a38320f3f16549e49f81fb2576e93cf
- this leaf
- fbdcc0c6067cfd27fd2a5edcc8a3f565b687f1afbc6f8621ddf2690cf93d310e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mv4bQU3Pn7odFnrTfaWV1hYVEIzTrQ6GA5+j+/jbVWrfTuBQSm+61aFt5Px3zSKM1+KjS9uL+yWI2iS/yUwnDw==