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
- e08aaa438bf7f4cc0f9c099d7563cdeebdc779f858beb2900aaa9e7ad959d18e
- request
- 0252adf29028b00d13e881af5f544e9f53de88e4d97247977d819d0afe369e27
- transaction
- 3786b333f0c2fc2b964d48f573dd571611e2bee962b64a8f061dffea81ee3bcecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37074
the chainentry 37074
- sealed to the entry before
- 82a8942d331790453b2726d82984cd39e633d85222f7f3d1d470e18f582b2a2b
- this leaf
- 1282cbcccd29771d5cf5b524b05dd8544518345be4fbc2eeb88d5d24b5d9242a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Lahf1+9qEtUhFgyUqrw8qgVL/lQ64EdX3bSH364ewtjhyHyiPXN1ssr05chvQzvcVKIUUeXdA5Zm2fS+KVXVBw==