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
- 62df5ab3ebd69a3975ff120574589244b8fc27c4b7a1acba2bd9613433c6077b
- request
- 75f721d2fe726d0b3ff0a6b4bc9832407c976534fd055355e2a60b46a6aca695
- transaction
- 72c240e9ad7ce0969ea6fab0128bb362876d62713cb4fc556fb0e001095555cacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72509
the chainentry 72509
- sealed to the entry before
- 8f74f162909cfab200ff47f3b9dc76c9704bd58cdddae4b0292e5fb4d7080370
- this leaf
- a800f8e1efa8b30951f65189fe14a84c24736e53cc4f50821cb4544a3e6fa55c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6siEgLzxxiVlALsiRd3qdBqMd0U/pBWdi6HwFzm21VklQ07I4lNFJjSTyQcb66cKN0GjgO8W0zpnczzODJuTBw==