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
- 72367a38d1b7e65a0d0f5cc650a8f31d18e8ec985917abc8886f40a27d572224
- request
- 74062b39c07d635080cfd201659b82cac3480766456a82df52bbf0adec09acef
- transaction
- f0300afb31eee6f2e5f590275855e78c5a7bf5f3b13cdc8f52553e73d1e07c00computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55523
the chainentry 55523
- sealed to the entry before
- 06cc90a3f312943979169c8a5a73f75e0874b658e96ec7fae7779bb68503528a
- this leaf
- 277c33e3671b7c9c4156e1cc57a1675e3563d1bb088053a25b85006ec734cc18
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TRBYbl53tZeqsbcWFeQezDxoY615JOHJPi3krYYu8RGgd14Hts/EpsB6aQIM1d03AiHTOtU/Sh52O6ruP2yIAg==