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
- e405c5e3b9b28816ea8ff4a4ac11b9c68de54b8779c21b77c0c36fd35cf302fb
- request
- 1083c801d9ac99aa0797a5888c8aed998143e6264ce28d6760f563e4179d8f00
- transaction
- f48c0d762ec8e5eaed404d49a31da33999b54ddc0ffdcedc33cb10497d9447ddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17544
the chainentry 17544
- sealed to the entry before
- e4f486170ec6503ab360082c570f0d62f35045481eb02930fc8e35da589045bf
- this leaf
- 8f32f7646eb716b8e272cab6b25204ee446158ec1f5e817a18567a739fe92aa2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xwsJgimjNHwGe6njVwC/WJMRkpUjUZ6yHrIasz9eblMAWqhmCG0i4tsDUhFhF+BW6MpopSefryl/aImFhBh5Bg==