Processing Methods

Web Redirect - Simple Payment

This is also a one-step (single API call with customer redirect) version of the Web Redirect transaction described above. As in the above, the card holder finalizes the transaction on a 3rd party site not in the merchant system; the card details (number, expiry date and security code or CVV / CV2) are only entered on the Intrapay secured page (or the Acqurier).
This API method is different from the above because the merchant does not need to send the customer information such as email, phone, names, address, city etc. The merchant only needs to send a unique reference of the transaction, the amount and currency, as well as computing a validpSign to protect the data.

To implement this method:

  1. The merchant securely obtains all the information needed to start a transaction;
  2. The merchant initiates a HTTPS POST or GET method to the Intrapay endpoint URL with all the necessary information as url-encoded key-value pairs and MUST redirect the customer in the same API call to the Payment platform. NOTE: The merchant should never send to the Intrapay system any parameters that include credit card data;
    URL: payment.intrapay.com/transaction/directPayment
  3. The system will respond to the Merchant by redirecting back the customer to the designated return URL used above;
  4. The Merchant shows the result of the transaction to the end user.

Web Redirect - Simple Payment fields

Order (pSign)Field NameDetailsMinMaxTypeRequired
01merchantIDMerchant id supplied by Intrapay18NumberYes
02amountThe purchase amount (ex. 1.99)112DecimalYes
03currencyThe purchase currency (ISO 4217)33StringYes
04orderIDThe unique Merchant Order ID164StringYes
05returnURLMerchant URL that will handle the customer redirect back1300StringYes
06notifyURLMerchant URL for server to server asynchronous notifications1300StringNo*
07descriptionTransaction or Product short description164StringNo
08csidPlease contact techsupport if you need to pass this parameter11000StringNo*
09pSignThe SHA signature used to secure protocol4040StringYes

* Please note that some Gateways / Banks do not support/use these parameters, or may consider them as mandatory! Our technical team will specify if any of these are required/supported.


Other Fields (Not included on pSign)

Field NameDetailsMinMaxTypeRequired
languagePage translation. Values: de, en, fr, tr. (Default: en)22StringNo

Example Web Redirect – Simple Payment request:

[POST URL] https://payment.intrapay.com/transaction/directPayment

[POST PARAMS]

merchantID=1&amount=50.00&currency=EUR&orderID=133668
&returnURL=https%3A%2F%2Fwww.mysite.com%2Freturn
&notifyURL=https%3A%2F%2Fwww.mysite.com%2Fnotify
&description=Payment+Shop+ID+226
&pSign=808bb38dbd345f4bca221f0118111d89bd707076

The Intrapay platform will redirect the user back to the Merchant`s Website using the `returnURL` sent earlier. For full reference (fields table and examples), please consult the section "Intrapay Response fields in customer redirect back" from the previous sections!


Example Web Redirect – Simple Payment response:

https://www.mysite.com/return?
responseCode=1&reasonCode=1
&transactionID=20150521-2CCD3B098A974FD81A23-EA22FE85577B85B32A2
&amount=50.00&currency=EUR&orderID=133668&executed=2015-05-
21+12%3A02%3A29&bankResultCode=022031&bankAuthCode=226884
&pSign=fff7dfaa0e0b35607c52e8d96b321cc842f0983c