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
- 6ac3bbdbb7ec76e0270d2ec379bfe55f498f23061d632b1dcbc92418bed65f0c
- request
- 8faea9223161626a0cc49c9dec6123a702274fd712871e8e539fd17ce1bb8e40
- transaction
- 9beb5121335f1f6aac0a7bb458ee5a47fec302b49728b5004480abfdab3c6c28computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1550
the chainentry 1550
- sealed to the entry before
- a81591c4c4aa88e782f526576229cde82cce2db24d4d68a1832fffeee8e282c3
- this leaf
- ca2b842998d6c793107b220499d603546f5fc682c17bbaf8a47ede4d70c13e6a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8RfQRWHcJuY8cikJgGXLprepGMigjEFfclR3Tfj212H4SeglEZqV0BaiF2T8el3jaKA5c2hEKaxedgAs24g0DQ==