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
- 1bcd4ced65b6d16a3467eaf5ed2e37bb2e9b8450898bc8537c9878c79d9e9d9f
- request
- cbf024d352dbd850e20edf90f3604be8bd58aba5e458e6b5cbc8e9b1c80bceb1
- transaction
- f0ee7c492fafbcb8ce526da7cc4c4d460484e8bfb3bcbe29de4f343cb803871dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65260
the chainentry 65260
- sealed to the entry before
- 13ac70b8d07b373372ac9732085b1834d4155f296df8dcdad97af78228729ec9
- this leaf
- b7171dcbc1e1268eeb355acd3945f4f34cc2d0b0aa89c4ecb7a0571667741b40
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dBQNK8VvlSn0D4KwtYeh/vi2gE4niJ8ggLJOV0ipNmHIiLS0U/guy5rglxtsQJYH2zy09g53NjamZBVNymR4CQ==