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
- 34734db779796437fdf11e83e23860e43687463e9dfa442c9b60ae5865aca44b
- request
- 3ad3e767a69216a2f97656ac367b88579141066a7afce87f17f770e6ad4e0835
- transaction
- 3c8179e3bf062194cdf7d2bbf5d2a80286d66a6cc512e33fdd9564f4a07642c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20820
the chainentry 20820
- sealed to the entry before
- 228925c8dbaa4845914d0def13e573b6b4d958f9d30cee9156bc09095853b454
- this leaf
- da7091b4835cc2a6ddf63a2fcebdabb95a65c2e278502b74c398404b17e111c8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pFrWTRUgrcUFpK1d+DBPwJB4yw6bYVrTC0MUe1YxiGVnC30dwCqdW4epgVkGDwASrWMRBCsYeDJ9BM/twX/tDw==