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
- cbfb5725ad1b25a5515d71c93060243dc80dbe46662b126da31c9ff524dc686b
- request
- 636631ff0a8e93444e5694b4373cd7530b794ffdbdbc186f4d2a35d441ab0030
- transaction
- ff4df67029f3ebf779b89a4cb822ad5c2c549ed82bb99c4e9195e6f3978ed26dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5990
the chainentry 5990
- sealed to the entry before
- 4a3609f9f0b4c476917eb265968569802f95e660e89a58ac90a83d6241067ad0
- this leaf
- 8ddc961f2b82663054bcee39bf0cc76c8b5564588f75263bf82ef938d6d8cbf9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aVjFq/uvX4I1MkN9cngwMRkW9t4uUfGUONmwlKBKi7Ty8vMkbB3/EgVRBEgCXmprw2CRDTMclFDnmawrXG6QAQ==