ideal Integration Guide Version 6.2.3

Transcription

1 ideal Integration Guide Version As of:

2 Table of Contents About ideal... 4 General information about ideal... 4 Process flow chart... 4 Paygate interface... 5 Definitions... 5 Calling the ideal interface... 6 Credit with reference... 8 Batch processing via the interface... 10

3 Document history Date Name Change Peter Posse Limitation of RefNr, Notice for credit.aspx Peter Posse TransactionID added Peter Posse First version based on Paygate Manual 6.10

4 About ideal: General information about ideal ABOUT IDEAL General information about ideal Like giropay in Germany, Dutch banks established the ideal money transfer standard. Approximately 50% of all e-commerce payments in the Netherlands are processed with ideal. Offering ideal is a vital success factor for e-commerce business wanting to sell in the Netherlands. The customer is using the familiar and trusted online banking of its own credit institution, just the same as with online banking. With online banking, the data disclosed in the online transfer is encrypted with SSL (Secure Sockets Layer) to prevent manipulation. Bank transfers with ideal are a guarantee of success in the Netherlands: About webshops and organizations offers ideal with approximately 50% of all e-commerce payments being processed with ideal. Monthly there are about 13 million transactions. Further information can be found ideal-website in Dutch and English ( Process flow chart Customer Merchant Paygate ideal Bank 1 ideal payment 2 ideal.aspx 3 InitTrx Request Response 4 5 Redirect to bank Notify 6 FinishTrx Request 7 9 Redirect ideal.aspx 8 FinishTrx Response with RedirectURL Notify OK/Failed Page ideal process flow Integration Guide Computop ideal 4

5 Paygate interface: Definitions PAYGATE INTERFACE Definitions Data formats: Format a as n an ans ns bool Description alphabetical alphabetical with special characters numeric alphanumeric alphanumeric with special characters numeric with special characters boolean expression (true or false) 3 fixed length with 3 digits/characters..3 variable length with maximum 3 digits/characters enum dttm enumeration of allowed values ISODateTime (YYYY-MM-DDDhh:mm:ss) Abbreviations: Abbreviation CND M O C Description condition mandatory optional conditional Notice: Please remind that the designations of parameters can be returned in upper case or lower case. Integration Guide Computop ideal 5

6 Paygate interface: Calling the ideal interface Calling the ideal interface To process a payment with online transfer with ideal, call up the following URL: Notice: For security reasons, Paygate rejects all payment requests with formatting errors. Therefore please use the correct data type for each parameter. The following table describes the encrypted payment request parameters: MerchantID ans..30 M MerchantID, assigned by Computop This parameter is to be passed in plain language. TransID ans..64 M TransactionID which should be unique for each payment RefNr ns..30 O Unique reference number. In case of using the EMS interface the length is limited to 15 chars. Amount n..12 M Amount in the smallest currency unit (e.g. EUR Cent) Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit). Currency a3 M Currency, three digits DIN / ISO 4217 OrderDesc ans..384 M Description of purchased goods, unit prices etc. Please note: The first 27 characters appear on the customer-account statement. You can view the full data in Computop Analytics. MAC an64 M Hash Message Authentication Code (HMAC) with SHA-256 algorithm UserData ans O If specified at request, Paygate forwards the parameter with the payment result to the shop URLSuccess ans..256 M Complete URL which calls up Paygate if payment has been successful. The URL may be called up only via port 443 This URL may not contain parameters: In order to exchange values between Paygate and shop, please use the parameter UserData. URLFailure ans..256 M Complete URL which calls up Paygate if payment has been unsuccessful. The URL may be called up only via port 443 This URL may not contain parameters: In order to exchange values between Paygate and shop, please use the parameter UserData. Response a7 O Status response sent by Paygate to URLSuccess and URLFailure, should be encrypted. For this purpose, transmit Response=encrypt parameter. URLNotify ans..256 M Complete URL which Paygate calls up in order to notify the shop about the payment result. The URL may be called up only via port 443 It may not contain parameters: Use the UserData parameter instead. ReqID ans..32 O To avoid double payments, enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction is submitted again with the same ReqID, Paygate will not carry out the payment, but will just return the status of the original transaction. BIC ans..11 O Bank Identifier Code IssuerID ans..11 MC Not with PPRO: BIC for the selected bank (see querying the stored ideal banks) Plain ans..50 O A value to be set by the merchant to return some information unencrypted, e.g. the MID Custom ans O The merchant can submit several values separated by which are returned unencrypted and separated by &. Custom=session=123 id=456 will change in the answer to Session=123&id=456 Parameters for online transfers with ideal Integration Guide Computop ideal 6

7 Paygate interface: Calling the ideal interface The following table gives the result parameters which the Paygate transmits to URLSuccess or URLFailure and URLNotify. If you have specified the Response=encrypt parameter, the following parameters are forwarded Blowfish encrypted to your system: MID ans..30 M MerchantID, assigned by Computop PayID an32 M ID assigned by Paygate for the payment, e.g. for referencing in batch files. XID an32 M ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate TransID ans..64 M Merchant s transaction number Status a..50 M OK (URLSuccess) or FAILED (URLFailure) Description ans M Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis! Code n8 M Error code according to Paygate Response Codes Excel file (part of the software client from RefNr ans..30 O Merchant s unique reference number UserData ans O If specified at request, Paygate forwards the parameter with the payment result to the shop MAC an64 M Hash Message Authentication Code (HMAC) with SHA-256 algorithm AccBank ans..20 MC Identification of the financial institution of the account holder (with PPRO only if Status=OK) AccOwner a..50 MC Name of the account holder (with PPRO only if Status=OK) IBAN ans..34 MC IBAN of the account holder (with PPRO only if Status=OK) BIC ans..11 MC BIC of the account holder (with PPRO only if Status=OK) PaymentPurpos e PaymentGuarant ee ans..26 C Only with PPRO: Purpose of payment a.12 C Only with PPRO: NONE= no payment guarantee, VALIDATED= customer account valid, but no payment guarantee, FULL= payment guarantee Notice: This parameter is only returned if the Status=OK. ErrorText ans..128 C Only with PPRO: Detailed PPRO error message. Notice: Is returned only if Status=FAILED. Use is possible only in agreement with Computop support. TransactionID an..20 O Only with PPRO: Unique transaction number from PPRO Plain ans..50 O A value to be set by the merchant to return some information unencrypted, e.g. the MID Custom ans O The merchant can submit several values separated by which are returned unencrypted and separated by &. Custom=session=123 id=456 will change in the answer to Session=123&id=456 Return parameters for URLSuccess, URLFailure and URLNotify with ideal Querying the stored ideal banks Paygate offers merchants the possibility to query which banks are stored for the merchant before the actual payment process. Since the configured bank list rarely changes, this does not need to be queried for each bank transfer. For this verification call up the following URL: Integration Guide Computop ideal 7

8 Paygate interface: Credit with reference The following table describes the encrypted payment request parameters: Please note that the Merchant-ID plus Len and Data must be transferred every time as with all Paygate requests: MerchantID ans..30 M MerchantID, assigned by Computop This parameter is to be passed in plain language. Parameters for requesting the stored ideal banks Please transfer the Merchant-ID both in the unencrypted as well as the encrypted string. The following table describes the result parameters, which Paygate sends in response: MerchantID ans..30 M MerchantID, assigned by Computop IdealIssuerList ans.. M The IdealIssuerList contains all banks stored for the merchant at the time of the query in the format IssuerID,Name,Country IssuerID = BIC of the bank Name = name of the bank Country = Name of the country for the bank (max. 128 charachters) Result parameters for requesting the stored ideal banks Credit with reference Credits (refunds) are possible via a Server-to-Server connection. Paygate permits only credits for ideal that reference on a captured transaction previously made via Paygate. The amount of the Credit is limited to the amount of the previous capture. To carry out a credit for ideal, please use the following URL: Notice: Please note that credits (refunds) for ideal can be processed only when using the processing partners EMS or EVO Payments. With a direct connection to the respective Dutch bank there are no credits possible via Paygate. Notice: For security reasons, Paygate rejects all payment requests with formatting errors. Therefore please use the correct data type for each parameter. The following table describes the encrypted payment request parameters: MerchantID ans..30 M MerchantID, assigned by Computop PayID an32 M ID assigned by Paygate for the payment to be credited TransID ans..64 M TransactionID which should be unique for each payment MAC an64 M Hash Message Authentication Code (HMAC) with SHA-256 algorithm Amount n..12 M Amount in the smallest currency unit (e.g. EUR Cent) Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit). Currency a..3 M Currency code, three digits DIN / ISO 4217 Integration Guide Computop ideal 8

9 Paygate interface: Credit with reference OrderDesc ans..768 O Description of refunded goods, unit prices, merchant s comment etc. Parameters for credits of ideal payments The following table describes the Paygate response parameters: MID ans..30 M MerchantID, assigned by Computop PayID an32 M ID assigned by Paygate for the payment, e.g. for referencing in batch files. XID an32 M ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate TransID ans..64 M Merchant s transaction number Status a..30 M OK or FAILED Description ans M Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis! Code n8 M Error code according to Paygate Response Codes Excel file (part of the software client from TransactionID an..20 O Only with PPRO: Unique transaction number from PPRO Result parameters for credits of ideal payments Integration Guide Computop ideal 9

10 Batch processing via the interface: Credit with reference BATCH PROCESSING VIA THE INTERFACE Basic information about using Batch files and about their structure you can be found in the Batch Manager manual. This section describes the parameters which must be transferred within the data set (Record) for executing a ideal credit and which information can be found within the response file about the payment status. Notice: Please note that Batch processing for ideal is possible only via PPRO connection. Following table gives an overview of all batch versions that are possible for a specific action an their specialities: Action Version Description Credit 1.0 / 2.0 Standard version without return of parameter Code 1.x / 2.x with RefNr (valid for all versions other than 1.0) Description of the possible batch versions The structure for an ideal payment within a Batch file to be submitted is the following: HEAD,<MerchantID>,<Date>,<Version> IDEAL,Credit,<PayID>,<TransID>,(<RefNr>),<Amount>,<Currency> FOOT,<CountRecords>,<SumAmount> The following table describes the individual fields and values used within the data set (record) within the batch file: Type a..11 M HEAD for Header, FOOT for Footer, IDEAL for ideal Action a..20 M The parameter Action defines the type of transaction: Credit Amount n..12 M Amount in the smallest currency unit (e.g. EUR Cent) Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit). Currency a3 M Currency code, three digits DIN / ISO 4217 TransID ans..64 M TransactionID which should be unique for each payment RefNr ans..30 O Unique reference number. In case of using the EMS interface the length is limited to 15 chars. PayID an32 M ID for this transaction given by Paygate Description of fields within the record for Batch files The record area within the response file for Batch transactions looks the following way: HEAD,<MerchantID>,<Date>,<Version> IDEAL,Credit,<PayID>,<TransID>,(<RefNr>),<Amount>,<Currency>,<Status>,<Code> FOOT,<CountRecords>,<SumAmount> The following table describes the response parameters which the Batch Manager saves in the Record area for each transaction (standard parameters not explained here, such as <TransID> or Integration Guide Computop ideal 10

11 Batch processing via the interface: Credit with reference <RefNR> and request parameters are returned unchanged and correspond to the call as specified in): Action a..20 M The parameter Action defines the type of transaction: Credit PayID an32 M ID for this transaction given by Paygate Status a..50 M OK or FAILED Code n8 M Error code according to Paygate Response Codes Excel file (part of the software client from Description of result parameters within the record for Batch files Integration Guide Computop ideal 11