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
- 7364ee1cad6c72e45c49ccdacd176d068ee6555759483095792fa89e980ecf8c
- request
- d1f609d82ed6716ae5ab091c1389ecf5a622b01339681763b6da9633533670c4
- transaction
- 1098d938442aff7ededbb6dab85ee4c45cadd94bcbd4f5f706b6ee07825eecc5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16428
the chainentry 16428
- sealed to the entry before
- eb26568f5ad967db98bfcb306825993068fc13bd676b34f6d446917e7bed3524
- this leaf
- 8809def814ea1dde49a35d8f174fea87aa06320ef140b1c3288c88e26589f740
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XzzcBEabyubyJpZcprbIaVyQQQtY3iqeWgt83ccJAUBT6IQ25WAWTxq/5JE1NLUPJlJ/1a7HyQxamfu3PrwODQ==