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
- abcf997809c3d833ee8755a27d35b5ca91c204333f8dc9c4e76db10680fe38b3
- request
- 866940b3ac7fdd4290cf4ace06ac0959217ea1944763781c165e4e55dbb6200a
- transaction
- d4348d87d978a6dca5c71c344b8f4d3ab933703946df68cf57ab9254562e8e2acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40597
the chainentry 40597
- sealed to the entry before
- f0a7c85efddc7e4b4b737a79c6c15e08c50847286c9b0cd1e794e5cda88d968f
- this leaf
- 21f70d34258c220830127a82ac7b324f6b5958992698ecfd27e0bdac4ce5248f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xE7vvK0WYuND7/PJHrTGmlGB5GOEzgi7yR2IK6ESYUMC8X09xnjnA8zO76Ebt8JvazRCmN0mHugLab9bJDpvDQ==