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
- f0608753249284f7332a0155649c7f36f8b4a78abdc4efa6537b55fbaada3a1d
- request
- 26e682254687aa9abed65ee70c4c3b37dfe4c383a397a54959ebb93a81d1fa9d
- transaction
- 4a00eec6db84d89b446b009d7f12f0557e5f9a553339431bf85ed01fd16ddb7ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44578
the chainentry 44578
- sealed to the entry before
- b010e81051a68e5064bf7b0d9f5d8d5731ca564c6e1059058d9d91fd471a3a3c
- this leaf
- f223abe21fd6936ef3a3a1ddc9899eef2b45272dad838c6492ea08135f36044d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- t6zKYbBoEbB2SR3pmU2Cv9XD3aJAx2kIzJRW1DwJO7JVCrCX2cd9RyMVRVGLC54cbNYQKxxPHb6G4alZ8+jKAQ==