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
- ce82bdd79b768bc5d56babaea3e2db689bd8e788137a5ae69a730228bb4770a5
- request
- 6b885329cb9812c3cc69d4237c260d928ec8317c7dd1547cab875e36cc8ff760
- transaction
- 1156cdd72d08cd8c16343ae0957eeb4f84854271ca28fec36ded92bbd3fa42fecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28808
the chainentry 28808
- sealed to the entry before
- 7407f4d5dab1abe76f87f836c79b0e38468c97fc4a0e6a63d53ee20a3c6a35fb
- this leaf
- 98f0b9a17e67277648e624726842b218a97b6a30cfaa6718af5de5f19ba39b1e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Va0EMvUIHIix2QNS6rpmU/lP6AO2mPwM6nyLjeUtbaxSmXUwFLZOgeIwlEiF3Sn3vkTWsIaQHg8AFjZjUNggCg==