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
- 5bf47008b627f3e04aa4fe8f979db3ebb0272cc193b0074768c085cc8b40e18a
- request
- 6941bc6533fc444295216d15eb0d19e2d7bd99f0f100657dc9cc84fd1bed2573
- transaction
- 99faf13923ae765e46bada7967b51a0ef5ff527af680019e899a2efdb728f09fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14639
the chainentry 14639
- sealed to the entry before
- 5c3cea88184ddd96ec95e7746f226334386e85f150c58c661cb87f5d08e1132d
- this leaf
- 62d3533baf9ef159fbdab210691ae2b3fd2afc6dbe22a44789236bc0bd93be74
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sKa+lDOCkbOBCr0F57zEM/Mqk+Xyk7y3NDtevcfZWnbr6cE4Xr43zfWMLjuWVW7b07dTtilpEsuLR7o5uXH9Ag==