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
- d0609fb5ac1c4cee24b9c350e431ac4004163127e86944bdf158d9a2cd1b6faf
- request
- 8702fc5864d2d6ce75a0b5865aa09724caecfd2ad6ac0694ae18579038bd4407
- transaction
- f720688043c9077bf56a34603f52e680eedaa8a7701355aae661dde409101549computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68789
the chainentry 68789
- sealed to the entry before
- b3cb1a95dddd36e1d490528f14f59d527106bb20cac6638f281034d699577d82
- this leaf
- 9d6565496fb443d2d29f8a07c7a0f0790a0d8d4b6cf3469d3cc3efb9c0ac6d9f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bXn9xvDGDgw4nAGeRLFleBEF/kRa8GFwSypTAT74Nd4ssuC4YUqBEWgOQpbq7W3+FrK6rwhC7JKtbIzBhuVVCg==