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
- 9379ee5d9e394e322be63bd2cc999177a0f8fb9dcc9690a3ceb127643644fc47
- request
- 1a974d1706b53e2203010e54e306d225df37f1a75af9c2f05b7536ad7500f335
- transaction
- c748eca9336e670df7254d9001cb9918e4da2202b97f2b11ad3e477f586b3ba3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2410
the chainentry 2410
- sealed to the entry before
- a14d89dd5a4acf13c0941fafdf122c92298f3012517f54759d7a932819fff750
- this leaf
- c7e1c0c56fac43ee6ead5cc1750138bb04d9e0f922adb3bd26a006df127dd817
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- G7ASs8ylKsVboUHZaRM7YDrUCF7UZaYGpMiaLtz0wXvS0TnVNmQmKvrLcDNl8X7qK+oXwaHwB9a1T3O9Xl/NBw==