We're finishing up the configuration of our Umbraco 7.1.4, TeaCommerce 2.3.1 store, but are running into one big issue.
We're adding the Authorize.Net payment form in a macro via the following script:
@Html.Raw( TC.GeneratePaymentForm( storeId, "<input type=\"submit\" id=\"checkout-submit\" value=\"Pay Now\" />" ) ) Note: The store id is set and the payment method is set in a previous step.
We followed the Authorize.Net / TeaCommerce instructions here: http://anders.burla.dk/umbraco/tea-commerce/using-authorize-net-with-tea-commerce/ and have setup all of the fields for the credit card payment setting in TeaCommerce. When we view the output from this form, there are not input fields for credit card number, expiration date, ccv or any expected credit card form fields. All we see is a Pay Now button. The output is shown below - note that all fields except the submit button are hidden inputs ( x_login and x_fp_hash values have been replaced ).
This is the way the payment provider works out of the box. Its a "redirect" payment provider where the customer is redirected to Authorize.Net payment form and complete the payment there. Makes sense?
If you want to make it inline you properly need to be PCI complient and other stuff :)
Tea Commerce Authorize.Net empty payment form
We're finishing up the configuration of our Umbraco 7.1.4, TeaCommerce 2.3.1 store, but are running into one big issue.
We're adding the Authorize.Net payment form in a macro via the following script:
@Html.Raw( TC.GeneratePaymentForm( storeId, "<input type=\"submit\" id=\"checkout-submit\" value=\"Pay Now\" />" ) )
Note: The store id is set and the payment method is set in a previous step.
We followed the Authorize.Net / TeaCommerce instructions here: http://anders.burla.dk/umbraco/tea-commerce/using-authorize-net-with-tea-commerce/ and have setup all of the fields for the credit card payment setting in TeaCommerce.
When we view the output from this form, there are not input fields for credit card number, expiration date, ccv or any expected credit card form fields. All we see is a Pay Now button. The output is shown below - note that all fields except the submit button are hidden inputs ( x_login and x_fp_hash values have been replaced ).
<form action="https://test.authorize.net/gateway/transact.dll" method="post">
<input type="hidden" id="x_login" name="x_login" value="OUR_LOGIN_CODE">
<input type="hidden" id="x_receipt_link_url" name="x_receipt_link_url" value="http://oursite.com/base/TC/PaymentContinue/1/AuthorizeNet/675d31ce-fa79-4969-9b71-7732b00da599.aspx">
<input type="hidden" id="x_cancel_url" name="x_cancel_url" value="http://oursite.com/base/TC/PaymentCancel/1/AuthorizeNet/675d31ce-fa79-4969-9b71-7732b00da599.aspx">
<input type="hidden" id="x_type" name="x_type" value="AUTH_CAPTURE">
<input type="hidden" id="x_version" name="x_version" value="3.1">
<input type="hidden" id="x_show_form" name="x_show_form" value="PAYMENT_FORM">
<input type="hidden" id="x_relay_always" name="x_relay_always" value="false">
<input type="hidden" id="x_relay_response" name="x_relay_response" value="TRUE">
<input type="hidden" id="x_receipt_link_method" name="x_receipt_link_method" value="LINK">
<input type="hidden" id="x_invoice_num" name="x_invoice_num" value="CART-36">
<input type="hidden" id="x_amount" name="x_amount" value="250.00">
<input type="hidden" id="x_fp_sequence" name="x_fp_sequence" value="886">
<input type="hidden" id="x_fp_timestamp" name="x_fp_timestamp" value="1402372333">
<input type="hidden" id="x_fp_hash" name="x_fp_hash" value="OUR_HASH">
<input type="submit" id="checkout-submit" value="Pay Now">
</form>
Hi
This is the way the payment provider works out of the box. Its a "redirect" payment provider where the customer is redirected to Authorize.Net payment form and complete the payment there. Makes sense?
If you want to make it inline you properly need to be PCI complient and other stuff :)
Kind regards
Anders
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.