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
- 92facc30c1cd82be1ea3326bdc181786aebb501db117185333a202abdff69685
- request
- cfcacd06326f1c042d64e83955a532889c1a05f4547f614407f727075853d7a3
- transaction
- 932dde16a2d2c86cca63aae510cfb2edc4451f9618204b028a51d4b0ac38ed81computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18003
the chainentry 18003
- sealed to the entry before
- 5e3cc2bd1a497b54b281e4dace5bc8480528bce9328421994a234e7520b54d9a
- this leaf
- a0418c7d6e30141da3363d36783de701e91137d502c6dfffdae9b78feef45716
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OQTN5vqxCi4w1dM4dZK8izSQNxfwige+ENgLcxI7L1IhzaZWJ/53BXQwwSNwurMQqL7dHXNrtUUq+QpCnmKyDQ==