PostFinance Payment Module Documentation v2

Last modified by Nick Weisser on Sat, July 10, 2010 06:16
Source|Old Revisions  

This is an old revision of the document!


Configuration

Note: replace “http://my-domain.com/” with the URL of your website

Once your test or production account is active, go to “Configuration / Technical information”. It contains five tabs.

Tab 1: Global transaction parameters

You can start with the default settings; fine-tune before going live.

Tab 2: Data and origin verification

URL of the merchant page containing the payment form that will call the page: orderstandard.asp (= this is the PostFinance payment page) and enter http://my-domain.com/postfinance/api/placeform

SHA-1-IN Signature minimum lenght: 16; must contain letters and digits

Tab 3: Transaction feedback

HTTP redirection in the browser * leave the four fields for the URLs empty * select “I want to receive transaction feedback parameters on the redirection URLs”

Direct HTTP server-to-server request * select “Always deferred (not immediately after the payment)” * enter in both fields http://my-domain.com/postfinance/api/postBack

SHA-1-OUT Signature minimum lenght: 16; must contain letters and digits

HTTP request for status changes * select “For each offline status change (payment, cancellation...)” * enter http://my-domain.com/postfinance/api/offlineProcess

Tab 4: Transaction e-mails

You can start with the default settings; fine-tune before going live.

Tab 5: Test info

Select “I want to simulate transaction results based on the card number” for a more convenient testing

simulate a “credit card accepted” transaction by using the test credit card number ending with 1 simulate a “credit card rejected” transaction by using the test credit card number ending with 3 simulate a “bank doesn’t answer” transaction by using the test credit card number ending with 6

Troubleshooting

Redirect to PostFinance not working

If you’re stuck on http://my-domain.com/postfinance/api/placeform at the end of the order process and are not redirected to PostFinance, make sure you copy app/design/frontend/default/default/postfinance.xml to your theme!

The following section contains a non-­exhaustive list of possible errors extracted from PostFinance’s Technical integration guide for e-­Commerce Version 4.4 which can be downloaded from the merchant GUI admin page.

unknown order/1/r

This error means that the referrer we detected is not a URL the merchant has entered in the URL field in the “Data and origin verification” tab, “Checks for e-Commerce” section of his Technical Information page. The merchant is sending us the form with the hidden fields containing the order information from a differ-­ ent page from the one(s) entered in the URL field in the “Data and origin verification” tab, “Checks for e-Commerce” section.

unknown order/0/r

This error means our server has not detected a referrer in the request we received. The merchant is send-­ ing us order details, but we do not know where they originated from. Please ensure that no methods are being used that blocking the referrer information (payment page in pop up, special web server configuration, customer’s browser configuration, ...). If the customer’s browser does not send the referrer information, we can bypass the referrer check if a SHASign is present and correct. (See Chapter 6.2)

unknown order/1/s

You will receive this error message if the SHASign sent in the hidden HTML fields for the transaction does not match the SHASign calculated at our end using the details of the order and the additional string (password/pass phrase) entered in the SHA-­1-­IN Signature field in the “Data and origin verification” tab, “Checks for e-Commerce” section of the Technical Information page.

unknown order/0/s

You will receive this error message if the “SHASign” field in the hidden HTML fields is empty but an additional string (password/pass phrase) has been entered in the SHA-­1-IN Signature field in the “Data and origin verification” tab, “Checks for e-Commerce” section of the Technical Information page, indicating you want to use a SHA signature with each transaction.

PSPID not found or not active

This error means the value you have entered in the PSPID field does not exist in the respective environ-­ ment (test or prod) or the account has not yet been activated. no <parameter> (for instance: no PSPID) This error means the value you sent for the obligatory <parameter> field is empty.

<parameter> too long (for instance: currency too long)

This error means the value in your <parameter> field exceeds the maximum length.

amount too long or not numeric: ... OR Amount not a number

This error means the amount you sent in the hidden fields either exceeds the maximum length or contains invalid characters such as . or , for intance.

not a valid currency : ...

This error means you have sent a transaction with a currency code that is incorrect or does not exist.

The currency is not accepted by the merchant

This error means you have sent a transaction in a currency that has not been registered in your account details.

ERROR, PAYMENT METHOD NOT FOUND FOR: ...

This error means the PM value you sent in your hidden fields does not match any of the payment methods you have selected in your account, or that the payment method has not been activated in your payment methods page.




 

Magento 2 GitHub Repository

Magento Job Board - Some sort of tag line goes here

Latest Posts| View all Jobs