Return success message for authorization and store the order values to be used on capture

Capture method depends on some information of the original order. To store these values we need to mock the authorization method too.

With the authorization mocked and storing the original order values we can make the capture method dynamic.
@dkonishi yes. seems a good plan.

@scudelletti I just like to be consistent. In the view I'd have to use string accessor so I used string accessor everywhere. But in fact symbol accessor saves more memory and some GC calls, not that it matters in this case.