Database Design for a Wizard's Output
Based on the complexity of your wizard, you may face here two possible scenarios. A wizard is nothing else but a paged form.
1. Your wizard has always the same amount of answers
1.a. The questions are always the same.
2.b. The questions may be different (opting between one payment method or the other, and thus the answer might be different)
2. Your wizard may have different amounts of questions, eg. you have a groups of answers that might be enabled or disabled.

So let's analyze case by case.
1.a That's easy, you have questions Q1, Q2, Q3, Q4... And you can simply store the answers in the same order as a simple series, as in your example.
1.b. This is a bit more complex, since storing simply the answers is not enough, as the questions are not the same. However, since we know the amount of answers is always the same you can create a table with as many columns as possible answers answers, adding a special columns to identify ambivalent questions. So the structure would be something like

CREATE TABLE FormResults (
A1 VARCHAR(50), -- eg. Name
A2 VARCHAR(50), -- eg. Surname
Q3 INTEGER, -- Q3 is the Payment method chosen, can be PayPal, credit card, bank transfer
A3 VARCHAR(50), -- This answer can be the email for PP, the card number, the bank account... corresponding to the Q3 chosen.
A4 DECIMAL(4,2) -- e.g. The amount
);


The benefit of this solution is that your table will be quite compact with nulls only when an answer is optional.

For the case 2, if the number of answers is variable that's the most complicated case. The easiest way to solve this is simply to create a table with columns for all possible answers. However depending on your wizard this may result in a table plenty of NULL values. If this is the case, and if this is a problem in your RDBMS, then you may create a table like

CREATE TABLE FormResults (
AnswerSetId INTEGER,
QuestionId INTEGER,
AnswerValue VARCHAR(50)
);


Being the PK (AnswerSetId, QuestionId)

Here you may find that different answer sets will have different number of rows in this table, depending on the choices of the user. The good thing of this solution is that it creates a very compact and easily indexable table.