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
- 219ce5ea2135a0adb08e2b2c23706cf96ddacaeaf954d59fa309c8709981b30d
- request
- 7aec4cfd920cde5d47159736c191abceff6430df0144ba923111abd28e0dad1c
- transaction
- 9127bdd94134ac67a785cf9977651ddd30b7fb580e072a5e45f07daefdbbc856computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11365
the chainentry 11365
- sealed to the entry before
- 0b831533d19233a1cad5681b1bfd83142e4beef014d0866f398042efbab5e291
- this leaf
- 730fe3b70783c4b9787f264b9efb8b362bf1adef5d926db8c15800535d8ec9bf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1CB0aXKVw2JUiv+HFhj06+aKvkmElaBAGUEGyY/vIptcje/kHxrGUj6aQaSmHsQgWGuA5PR2HD6HvMDk+TlFDw==