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
- 48fe189bbaac5b893a3df5bbed6d0f59e06c84ddb870d9f862e625e5dda82d29
- request
- db7fe4a878c81401f7e1f06b9dcdec9539f3ced72b330cbfdc3347a38c91007f
- transaction
- 19a3025ce1a5ccbd50f82ce2bda38bae9324710c29bfa219c0238a623e5a8d27computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77035
the chainentry 77035
- sealed to the entry before
- ee55a3a6b8e4767ad513f954644a66ecadbe7058df5b7ae1058de103d1265ae4
- this leaf
- 30740a345c2e5705345cfb23618e034706a68c2b831665fc931e61b61764bd38
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hBIK4xPXxIwNuWm8QRTA6B9lg2J3SIdyH7QyKK1J6T5trDsaiZE9qrssf+n7+efBuNxJKzZeKg1Fs2cQhUBGCQ==