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
- 3ad4f759c082dee97031a9c2c7ab14d5184b3a38c09356d047cba0da5ab5b2af
- request
- b20be59e2665f3511474139911f868abeaf62e3598448c3effb194964d917a91
- transaction
- 4c252c3649427f63878607dcb80881c7b807cbd704733a74fc89619d88aee52ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3579
the chainentry 3579
- sealed to the entry before
- 5594235745db1e67053a1f70fcd09d2e3eeca0cc7f999126b1788379f5c76cb0
- this leaf
- f8019972ff631d8b629ad1be3fca93d4e91392efb0cced00f80729de3afb5d6e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5HcGF7NsiqWp6JUCnW8Of65tbchhufw/KLg5z9zETZ7L94pfu1cNgDTLV0wwgDfRSmZV9WE2cZGcDRmrf8s3Bg==