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
- 392dbc1d0eb5ed3d77f2c5358fd2667c1635c07fa826ef0627bdab1fc48b83cc
- request
- dc22093114378cae961f86eed86512079e8f2ce00163d636e3b4bd9be5b31e9a
- transaction
- 57e351a46751fe05b9d77e5fbfe4e653b4b15af2d2a0d0e3a5d0e34eed450150computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56104
the chainentry 56104
- sealed to the entry before
- 66af5b13cc10a0fdde9f06af1bc28704470967d386ca5940754100d91ad5dcfb
- this leaf
- 8a322a560ae9d96b2e96fe2d484ebcf3fff7474cc49934ddf13a0d7fe72c884e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- azibtjItGks6TZ0z1jNWEH0A7MiFCyfjARNz+wOvL+Y5cXhoshWI/LphZMmCCJc0u76riXJBtrEMYOdB3l/WBg==