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
- 0c31785c9b533154f6483680bed004eeea88938e92802284005c3efb36796c0a
- request
- 857a5d9d877d75e048ae157555a8cb921df6de9e24d0b5f5eb274850db98808a
- transaction
- 8c5ebcf5f7913f3cb8af89ec6d3c0d7a1fd4e442c2a9e35ad4b0399cd3153b46computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2160
the chainentry 2160
- sealed to the entry before
- 6d3d5b6898a0ab2006662c51526a945d547f0d22ff3432790682a0c7ef1d887c
- this leaf
- 9ba97285e0af0905e0cedfb547bda4a71f3478f0dd91247e6c94ea00b83195af
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dxLNddf9MDnK8y4LSZjmNHnI619RKGPaHRmm8wSeckTme/ARX+zEPnVgQmWNNZXrZvq2V89pJ/W0TMH0mFvjBg==