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
- 93987df530f37d24f5a07c58254fa7e84942e68a05542911060d444a3061cf9b
- request
- ae106ac2cb84fba1ec20ad0743e48c84d7c04368af1de9ad60d4ce519004da62
- transaction
- b7d50dd670bf0f75886152e9da53c3d0c63d2ded82bd7257f0af939c699b0697computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9496
the chainentry 9496
- sealed to the entry before
- 410458c6b5f35dfdc38786632ec5846e4c0d6fd3a4f386b7ee709bee4439559b
- this leaf
- daed8a8ba1cf70665ee80d29c60e1dcfe6e826b545cffb85dfbc8e25736e59dc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Bea9LAb/JZr8EVInjZUdjen5Q6yLrHlZVlHX5TT3biuxOZP+E8PwFvK/r7E8MK8AxMM84rXhroMSZpi+XaBSDg==