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
- ca57e12a78dbe650a9456faa8da7a2048b16a51a85bed7d76dbe379fb4e4fbfa
- request
- 791efaa1cfbe87a664fb284c9a38a6e510688c5caa4b44560d0210e124bdd722
- transaction
- 32537370c07f40029289d7447764edeb3e4d611d1ab8f241c58b4579f4404777computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73114
the chainentry 73114
- sealed to the entry before
- e695520965df3faf9aca4cca0575a101134581fa0a99082851bedbf816b4d5bb
- this leaf
- 66efe009ce3523647bcbf93bd3e444fdd9d5731b24e1fb4184f903958fcf5da7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MHjLYzboYYceetk/edMgzg4DU1+F4rI7zkVy0AT4PIHrTI3iAFeLmJHDZItgFjB98AeoLJpWzPFYjymWr9/vDA==