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
- c6f21ea79db9b4254d5da3b58b4009cee4ae86bce724f447d11f0b392b81b454
- request
- 71c6720b5cad952c13e393e41144b8499c9edf09db4c28efd1b229dd13456736
- transaction
- 011775ead30fc1d65bf405e70c8498e430b8e74d4116dde823ed4069e8342d0bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42296
the chainentry 42296
- sealed to the entry before
- 8a2c362a04771ea0e66adb96e7f396c062cad1bc185caddf8030cfb04d8b61a9
- this leaf
- b2a9274490a17280df2390c0e5edf7adc18730626e05cb348c451d4b194815dd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oLEyIag2oUJ27xpipRQnP4bcAlHF22nuH8R5e49DHdT96g/tqeYjdQSsEy5eHVShnRavOcFc4+YXU98SdTjQAg==