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
- b232e9d76b183c1c7fc95f65bd94c6f83740201ec4309365a1653da290d9c6ea
- request
- c1f4cfc8cc3c2ec6f52d251b6fa3a75fdabd018074f5faa91bb8ab84425c8c33
- transaction
- 0d2866df7193e1bd6ba85c20f3f352f0a59bff099c44c71336d4e901963fd578computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33737
the chainentry 33737
- sealed to the entry before
- 68f0c6a5f2d5bb4e4956031827028817c484b337984a556dbb21511cba758eb8
- this leaf
- b65376e7966c1b8f747f962ae6cbea614392946d227669852996b703913d6836
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L/BNYG+roeQyoo98nga0G4DYBQGXGE/kDHn6ecjeiOZ3QT+PXavPvd6Vu+MChpCOxJQl5qlntZXE8dA1moxJCw==