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
- 0035e9367be3439b6a2346db60ff8e3baa003696737e908e28584f1b7cc513b6
- request
- 81c441e9b9138c471849f7748f092bf9d4cad1e661f42cb52bcfaac7f4badc28
- transaction
- 4ed9d4a48959e7102f5c7c3491bf2f63ff0262285b123c471a2160d03eba552ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34454
the chainentry 34454
- sealed to the entry before
- 7c2cceace49aa79beb4a213a7e6c76f0072c40e032da2c106ab50fd63eaa01b0
- this leaf
- 0573213f5184f82934e6d2c560f9d49fdb19bee668236bd64c10dd59e6cc2600
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ctBD2cn+5Wx6SrZ9MECPOWfdIhZkqNbYyURV0K6kNUPx/y/otjdrgZWvTHZo3E1GbN22npco/qgxsvZK+KtFBw==