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
- a73de08b12ffa807e22990062a3dbd5b206616bbd19f9a912e45db1f79a0d38d
- request
- 817d7b750e41f45eb97650a9f796ab6ef40605ad48b53ca75acacc129003f82f
- transaction
- 5b4926e16dd33ab9da90b6bcb6e536eb42663f0558665f686c33dade4e0d2a5dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 341
the chainentry 341
- sealed to the entry before
- fd5b1ce590501f6fa97f0dced2e7ee5aa2339daacbf64e4064ca7626b929ed78
- this leaf
- 341ea79270f805a50760dfa45c34c91f31b47b65f4c3b3eba6fc5d29e94e9eef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BlY80QQeyhqovHeIz3lkXWkBswSdE+GYHpcAKcqxrnH93kVPfOwIPyG3AWbwwmU4kPFAKv3hf3+ByiEcJB+pDw==