eps | Computop Documents

About eps

General information about eps

In Austria Computop Paygate supports online money transfer with the Austrian Electronic Payment Standard (EPS). EPS is an established system for e-commerce payments in Austria offering a payment guarantee to the merchant. The customer can use 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.

Logo

COO 6505 1000 12 121220

Info

In Austria the online bank transfer with eps is very widespread in E-commerce and thus an interesting addition to the payment mix. Additionally the merchant gets a payment guarantee.

Type

Payments by Online Bank Transfer

Further information can be found on the webpage of eps (https://eps-ueberweisung.at/).

Process flow chart

eps process flow

Paygate interface

Definitions

Data formats

Format

Description

alphabetical

alphabetical with special characters

numeric

alphanumeric

ans

alphanumeric with special characters

numeric with special characters

bool

boolean expression (true or false)

fixed length with 3 digits/characters

..3

variable length with maximum 3 digits/characters

enum

enumeration of allowed values

dttm

ISODateTime (YYYY-MM-DDThh:mm:ss)

Abbreviations

Abbreviation

Description

Comment

CND

condition

mandatory

If a parameter is mandatory, then it must be present

optional

If a parameter is optional, then it can be present, but it is not required

conditional

If a parameter is conditional, then there is a conditional rule which specifies whether it is mandatory or optional

Notice: Please note that the names of parameters can be returned in upper or lower case.

Calling the eps interface

The eps connection with a Paygate form can be either direct or via PPRO, where the interface form and process are largely identical. With the PPRO connection there are a few added parameters which are explained separately in the table. Subsequent credits and batch transfer credits can only be made with the PPRO connection.

To make a payment in Austria with eps online transfer via a Paygate form, please use the following URL:

https://www.computop-paygate.com/eps.aspx

Notice: For security reasons, Computop 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:

Notice: An eps connection via iFrame is not possible due to eps regulations and will be prevented technically.

Key	REST	Format	CND	Description
MerchantID	BasicAuth.Username	ans..30	M	MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too.
TransID	"transactionId": "..."	ans..64	M	TransactionID provided by you which should be unique for each payment
RefNr	"referenceNumber": "..."	ns..30	M	Unique reference number. In case of PPRO: Only characters a-zA-Z0-9,-_ are allowed, format ans..40.
Amount	"amount": { "value": ...}	n..10	M	Amount in the smallest currency unit (e.g. EUR Cent). Please contact the Computop Helpdesk, if you want to capture amounts <100 (smallest currency unit).
Currency	"amount": { "currency": "..."}	a3	M	Currency, three digits DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: A1 Currency table
OptionDate	"payment": {"eps": {"desiredPaymentExecutionDate": "..."}}	ans10	OC	Not with PPRO: desired payment execution date in the format YYYY-MM-DD
OrderDesc	"order": {"description[0]": "..."}	ans..768	M	Intended use on statement of account (max 35 digits) With PPRO: Description of purchased goods, unit prices etc.
OrderDesc2	"order": {"description[1]": "..."}	ans..384	C	Not with PPRO: Number and description of purchased products, individual prices, comma-separated list, no special characters allowed
AccOwner	"payment": {"eps": {"account": {"accountHolder": "..."}}}	ans3..50	OC	Obligatory for PPRO: Name of account holder
IBAN	"payment": {"eps": {"account": {"number": "..."}}}	ans..34	OC	Obligatory for PPRO: International Bank Account Number for SEPA
BIC	"payment": {"eps": {"account": {"code": "..."}}}	ans..11	OC	Obligatory for PPRO: Bank Identifier Code for SEPA
MAC	–––	an64	M	Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: HMAC Authentication (Request) HMAC Authentication (Notify)
UserData	"metadata[userData]": "..."	ans..1024	O	If specified at request, Paygate forwards the parameter with the payment result to the shop.
URLSuccess	"urls": {"success": "..."}	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. Common notes: We recommend to use parameter "response=encrypt" to get an encrypted response by Paygate However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.
URLFailure	"urls": {"failure": "..."}	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. Common notes: We recommend to use parameter "response=encrypt" to get an encrypted response by Paygate However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.
Response	–––	a7	O	Status response sent by Paygate to URLSuccess and URLFailure, should be encrypted. For this purpose, transmit Response=encrypt parameter.
URLNotify	"urls": {"notify": "..."}	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 UserDataparameter instead. Common notes: Before follow-up actions (capture / credit / reversal) are carried out on an existing transaction, the first Notify must have been answered by the shop. Fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.
ReqId	"requestId": "..."	ans..32	O	To avoid double payments or actions (e.g. by ETM), enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction or action is submitted again with the same ReqID, Computop Paygate will not carry out the payment or new action, but will just return the status of the original transaction or action. Please note that the Computop Paygate must have a finalized transaction status for the first initial action (authentication/authorisation). This does not apply to 3-D Secure authentications that are terminated by a timeout. The 3-D Secure Timeout status does not count as a completed status in which the ReqID functionality on Paygate does not take effect. Submissions with identical ReqID for an open status will be processed regularly. Notice: Please note that a ReqID is only valid for 12 month, then it gets deleted at the Paygate.
SellingPoint	"payment": {"eps": {"sellingPoint": "..." }}	ans..50	C	Only with PPRO: Selling point
Service	"payment": {"eps": {"service": "..." }}	ans..50	C	Only with PPRO: products or service sold
Channel	"channel": {"code": "..."}	ans..64	OC	Only with PPRO: configuration channel of the PPRO contract (account and ContractID are stored in the system). If it exists, it may overwrite channels stored in the system
Language	"language": "..."	a2	O	Only with PPRO: 2-letter language code (e.g.. de) that should be preferred when presenting payment pages to the consumer
Plain	"metadata[plain]": "..."	ans..50	O	A single value to be set by the merchant to return some information unencrypted in response/notify, e.g. the MID. "Plain"-parameter is part of encrypted "Data" in Computop Paygate and therefore protected against manipulation.
Custom	"metadata": "..."	ans..1024Format	O	"Custom"-parameter is added to the request data before encryption and is part of encrypted "Data" in Computop Paygate request. By this they are protected against manipulation by a consumer. The Custom-value is added to the Computop Paygate response in plain text and the "\|" is replaced by a "&". By this you can put a single value into Custom-parameter and get multiple key-value-pairs back in response for your own purpose. Please find a sample here: Custom

Key

REST

Format

CND

Description

MerchantID

BasicAuth.Username

ans..30

MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too.

TransID

"transactionId": "..."

ans..64

TransactionID provided by you which should be unique for each payment

RefNr

"referenceNumber": "..."

ns..30

Unique reference number.

In case of PPRO: Only characters a-zA-Z0-9,-_ are allowed, format ans..40.

Amount

"amount": { "value": ...}

n..10

Amount in the smallest currency unit (e.g. EUR Cent). Please contact the Computop Helpdesk, if you want to capture amounts <100 (smallest currency unit).

Currency

"amount": { "currency": "..."}

Currency, three digits DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: A1 Currency table

OptionDate

"payment": {"eps": {"desiredPaymentExecutionDate": "..."}}

ans10

Not with PPRO: desired payment execution date in the format YYYY-MM-DD

OrderDesc

"order": {"description[0]": "..."}

ans..768

Intended use on statement of account (max 35 digits)

With PPRO: Description of purchased goods, unit prices etc.

OrderDesc2

"order": {"description[1]": "..."}

ans..384

Not with PPRO: Number and description of purchased products, individual prices, comma-separated list, no special characters allowed

AccOwner

"payment": {"eps": {"account": {"accountHolder": "..."}}}

ans3..50

Obligatory for PPRO: Name of account holder

IBAN

"payment": {"eps": {"account": {"number": "..."}}}

ans..34

Obligatory for PPRO: International Bank Account Number for SEPA

BIC

"payment": {"eps": {"account": {"code": "..."}}}

ans..11

Obligatory for PPRO: Bank Identifier Code for SEPA

MAC

–––

an64

Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:

UserData

"metadata[userData]": "..."

ans..1024

If specified at request, Paygate forwards the parameter with the payment result to the shop.

URLSuccess

"urls": {"success": "..."}

ans..256

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.

Common notes:

We recommend to use parameter "response=encrypt" to get an encrypted response by Paygate
However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.

URLFailure

"urls": {"failure": "..."}

ans..256

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.

Common notes:

We recommend to use parameter "response=encrypt" to get an encrypted response by Paygate
However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.

Response

–––

Status response sent by Paygate to URLSuccess and URLFailure, should be encrypted. For this purpose, transmit Response=encrypt parameter.

URLNotify

"urls": {"notify": "..."}

ans..256

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 UserDataparameter instead.

Common notes:

Before follow-up actions (capture / credit / reversal) are carried out on an existing transaction, the first Notify must have been answered by the shop.
Fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.

ReqId

"requestId": "..."

ans..32

To avoid double payments or actions (e.g. by ETM), enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction or action is submitted again with the same ReqID, Computop Paygate will not carry out the payment or new action, but will just return the status of the original transaction or action.

Please note that the Computop Paygate must have a finalized transaction status for the first initial action (authentication/authorisation). This does not apply to 3-D Secure authentications that are terminated by a timeout. The 3-D Secure Timeout status does not count as a completed status in which the ReqID functionality on Paygate does not take effect. Submissions with identical ReqID for an open status will be processed regularly.

Notice: Please note that a ReqID is only valid for 12 month, then it gets deleted at the Paygate.

SellingPoint

"payment": {"eps": {"sellingPoint": "..." }}

ans..50

Only with PPRO: Selling point

Service

"payment": {"eps": {"service": "..." }}

ans..50

Only with PPRO: products or service sold

Channel

"channel": {"code": "..."}

ans..64

Only with PPRO: configuration channel of the PPRO contract (account and ContractID are stored in the system). If it exists, it may overwrite channels stored in the system

Language

"language": "..."

Only with PPRO: 2-letter language code (e.g.. de) that should be preferred when presenting payment pages to the consumer

Plain

"metadata[plain]": "..."

ans..50

A single value to be set by the merchant to return some information unencrypted in response/notify, e.g. the MID.

"Plain"-parameter is part of encrypted "Data" in Computop Paygate and therefore protected against manipulation.

Custom

"metadata": "..."

ans..1024Format

"Custom"-parameter is added to the request data before encryption and is part of encrypted "Data" in Computop Paygate request. By this they are protected against manipulation by a consumer.

The Custom-value is added to the Computop Paygate response in plain text and the "|" is replaced by a "&". By this you can put a single value into Custom-parameter and get multiple key-value-pairs back in response for your own purpose.

Please find a sample here: Custom

Parameters for online transfers with eps

In case of using REST API

In case of using REST API you will always receive a link where the merchant has to redirect the consumer to complete the payment.

REST

Format

CND

Description

"paymentId": "..."

an32

May be "00000000000000000000000000000000" if not yet set by Computop Paygate

"_Links.self.type": "..."

an..20

"application/json"

"_Links.redirect.href": "..."

an..1024

Merchant needs to redirect consumer to this URL to complete payment

"_Links.redirect.type": "..."

an..20

"text/html"

Merchant can use inquire.aspx

In case of using Key-Value-Pair API

The following table gives the result parameters which Computop Paygate transmits to URLSuccess or URLFailure and URLNotify. If you have specified the Response=encrypt parameter, the following parameters are sent Blowfish encrypted to your system:

pls. be prepared to receive additional parameters at any time and do not check the order of parameters

the key (e.g. MerchantId, RefNr) should not be checked case-sentive

Key	Format	CND	Description
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 as well as for capture or credit request.
XID	an32	M	ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate
TransID	ans..64	M	TransactionID provided by you which should be unique for each payment
Status	a..50	M	OK, AUTHORIZED (URLSuccess) or FAILED (URLFailure). with PPRO also AUTHORIZE_REQUEST
Description	ans..1024	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	an8	M	Error code according to Paygate Response Codes (A4 Error codes)
RefNr	ns..30	O	Unique reference number. In case of PPRO: Only characters a-zA-Z0-9,-_ are allowed, format ans..40.
MAC	an64	M	Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: HMAC Authentication (Request) HMAC Authentication (Notify)
UserData	ans..1024	O	If specified at request, Paygate forwards the parameter with the payment result to the shop.
AccOwner	ans3..50	M	Name of account holder
IBAN	ans..34	OC	Obligatory for PPRO: International Bank Account Number for SEPA
BIC	ans..11	OC	Obligatory for PPRO: Bank Identifier Code for SEPA
PaymentPurpose	ans..26	C	Only with PPRO: Purpose of payment
PaymentGuarantee	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 Helpdesk.
TransactionID	an..20	O	Only with PPRO: Unique transaction number from PPRO
Plain	ans..50	O	A single value to be set by the merchant to return some information unencrypted in response/notify, e.g. the MID. "Plain"-parameter is part of encrypted "Data" in Computop Paygate and therefore protected against manipulation.
Custom	ans..1024	O	"Custom"-parameter is added to the request data before encryption and is part of encrypted "Data" in Computop Paygate request. By this they are protected against manipulation by a consumer. The Custom-value is added to the Computop Paygate response in plain text and the "\|" is replaced by a "&". By this you can put a single value into Custom-parameter and get multiple key-value-pairs back in response for your own purpose. Please find a sample here: Custom

Key

Format

CND

Description

mid

ans..30

MerchantID, assigned by Computop

PayID

an32

ID assigned by Paygate for the payment, e.g. for referencing in batch files as well as for capture or credit request.

XID

an32

ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate

TransID

ans..64

TransactionID provided by you which should be unique for each payment

Status

a..50

OK, AUTHORIZED (URLSuccess) or FAILED (URLFailure).

with PPRO also AUTHORIZE_REQUEST

Description

ans..1024

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

an8

Error code according to Paygate Response Codes (A4 Error codes)

RefNr

ns..30

Unique reference number.

In case of PPRO: Only characters a-zA-Z0-9,-_ are allowed, format ans..40.

MAC

an64

Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:

UserData

ans..1024

If specified at request, Paygate forwards the parameter with the payment result to the shop.

AccOwner

ans3..50

Name of account holder

IBAN

ans..34

Obligatory for PPRO: International Bank Account Number for SEPA

BIC

ans..11

Obligatory for PPRO: Bank Identifier Code for SEPA

PaymentPurpose

ans..26

Only with PPRO: Purpose of payment

PaymentGuarantee

a..12

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

Only with PPRO: Detailed PPRO error message.

Notice: Is returned only if Status=FAILED. Use is possible only in agreement with Computop Helpdesk.

TransactionID

an..20

Only with PPRO: Unique transaction number from PPRO

Plain

ans..50

A single value to be set by the merchant to return some information unencrypted in response/notify, e.g. the MID.

"Plain"-parameter is part of encrypted "Data" in Computop Paygate and therefore protected against manipulation.

Custom

ans..1024

"Custom"-parameter is added to the request data before encryption and is part of encrypted "Data" in Computop Paygate request. By this they are protected against manipulation by a consumer.

Please find a sample here: Custom

Result parameters for URLNotify, URLSuccess and URLFailure in case of eps

Credit with reference

Credits (refunds) are possible via a Server-to-Server connection. Eps credits are only allowed with the PPRO connection. Paygate permits only credits for eps that reference on a capture previously made via Paygate. The amount of the Credit is limited to the amount of the previous capture.

To carry out a credit with a reference transaction, please use the following URL:

https://www.computop-paygate.com/credit.aspx

Notice: For security reasons, Computop 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:

Key	REST	Format	CND	Description
MerchantID	BasicAuth.Username	ans..30	M	MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too.
PayID	"paymentId": "..."	an32	M	ID assigned by Paygate for the payment to be credited
TransID	"transactionId": "..."	ans..64	M	TransactionID provided by you which should be unique for each payment
MAC	–––	an64	M	Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: HMAC Authentication (Request) HMAC Authentication (Notify)
Amount	"amount": { "value": ...}	n..10	M	Amount in the smallest currency unit (e.g. EUR Cent). Please contact the Computop Helpdesk, if you want to capture amounts <100 (smallest currency unit).
Currency	"amount": { "currency": "..."}	a3	M	Currency, three digits DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: A1 Currency table
ReqId	"requestId": "..."	ans..32	O	To avoid double payments or actions (e.g. by ETM), enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction or action is submitted again with the same ReqID, Computop Paygate will not carry out the payment or new action, but will just return the status of the original transaction or action. Please note that the Computop Paygate must have a finalized transaction status for the first initial action (authentication/authorisation). This does not apply to 3-D Secure authentications that are terminated by a timeout. The 3-D Secure Timeout status does not count as a completed status in which the ReqID functionality on Paygate does not take effect. Submissions with identical ReqID for an open status will be processed regularly. Notice: Please note that a ReqID is only valid for 12 month, then it gets deleted at the Paygate.

Key

REST

Format

CND

Description

MerchantID

BasicAuth.Username

ans..30

MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too.

PayID

"paymentId": "..."

an32

ID assigned by Paygate for the payment to be credited

TransID

"transactionId": "..."

ans..64

TransactionID provided by you which should be unique for each payment

MAC

–––

an64

Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:

Amount

"amount": { "value": ...}

n..10

Amount in the smallest currency unit (e.g. EUR Cent). Please contact the Computop Helpdesk, if you want to capture amounts <100 (smallest currency unit).

Currency

"amount": { "currency": "..."}

Currency, three digits DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: A1 Currency table

ReqId

"requestId": "..."

ans..32

Notice: Please note that a ReqID is only valid for 12 month, then it gets deleted at the Paygate.

Parameters for credits of eps payments

The following table describes the result parameters with which the Computop Paygate responds to your system

pls. be prepared to receive additional parameters at any time and do not check the order of parameters

the key (e.g. MerchantId, RefNr) should not be checked case-sentive

Key	REST	Format	CND	Description
mid	"merchantId": "..."	ans..30	M	MerchantID, assigned by Computop
PayID	"paymentId": "..."	an32	M	ID assigned by Paygate for the payment, e.g. for referencing in batch files as well as for capture or credit request.
XID	"xId": "..."	an32	M	ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate
TransID	"transactionId": "..."	ans..64	M	TransactionID provided by you which should be unique for each payment
Status	"status": "OK" "status": "AUTHORIZED" "status": "FAILED"	a..50	M	OK or AUTHORIZED (URLSuccess) as well as FAILED (URLFailure)
Description	"description": "..."	ans..1024	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	"code": ...	an8	M	Error code according to Paygate Response Codes (A4 Error codes)
ErrorText	"errorText": "..."	ans..128	C	Detailed PPRO error message. Notice: Is returned only if Status=FAILED. Use is possible only in agreement with Computop Helpdesk.

Key

REST

Format

CND

Description

mid

"merchantId": "..."

ans..30

MerchantID, assigned by Computop

PayID

"paymentId": "..."

an32

ID assigned by Paygate for the payment, e.g. for referencing in batch files as well as for capture or credit request.

XID

"xId": "..."

an32

ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate

TransID

"transactionId": "..."

ans..64

TransactionID provided by you which should be unique for each payment

Status

"status": "OK"

"status": "AUTHORIZED"

"status": "FAILED"

a..50

OK or AUTHORIZED (URLSuccess) as well as FAILED (URLFailure)

Description

"description": "..."

ans..1024

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

"code": ...

an8

Error code according to Paygate Response Codes (A4 Error codes)

ErrorText

"errorText": "..."

ans..128

Detailed PPRO error message.

Notice: Is returned only if Status=FAILED. Use is possible only in agreement with Computop Helpdesk.

Result parameters for credits of eps payments

Batch processing via the interface

Basic information about using Batch files and about their structure can be found in the Batch Manager manual. Within batch processing not alle functions are available which are usually available for the online interface.

This section describes the parameters which must be transferred with the data set (Record) for executing an eps credit and which information can be found within the response file about the payment status.

Notice: Please note that Batch processing for eps 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 eps credit within a Batch file to be submitted is the following:

1
HEAD,<MerchantID>,<Date>,<Version>
2
EPS,Credit,<PayID>,<TransID>,(<RefNr>),<Amount>,<Currency>
3
FOOT,<CountRecords>,<SumAmount>

Example for Master MID function:

1
HEAD,[Master]MerchantID,Date,2.x
2
Type,Action,[Slave]MID,Amount,Currency,TransID,Data (depends on Action)
3
FOOT,CountRecords,SumAmount

The following table describes the individual fields and values used within the data set (record) in the batch file:

Key	Format	CND	Description
Type	a..11	M	HEAD for Header, FOOT for Footer, EPS for direct eps
Action	a..20	M	The parameter Action defines the type of transaction: Credit
Amount	n..10	M	Amount in the smallest currency unit (e.g. EUR Cent). Please contact the Computop Helpdesk, if you want to capture amounts <100 (smallest currency unit).
Currency	a3	M	Currency, three digits DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: A1 Currency table
TransID	ans..64	M	TransactionID provided by you which should be unique for each payment
RefNr	ns..30	O	Unique reference number. In case of PPRO: Only characters a-zA-Z0-9,-_ are allowed, format ans..40.
PayID	an32	M	ID assigned by Paygate for this transaction

Key

Format

CND

Description

Type

a..11

HEAD for Header, FOOT for Footer, EPS for direct eps

Action

a..20

The parameter Action defines the type of transaction: Credit

Amount

n..10

Amount in the smallest currency unit (e.g. EUR Cent). Please contact the Computop Helpdesk, if you want to capture amounts <100 (smallest currency unit).

Currency

Currency, three digits DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: A1 Currency table

TransID

ans..64

TransactionID provided by you which should be unique for each payment

RefNr

ns..30

Unique reference number.

In case of PPRO: Only characters a-zA-Z0-9,-_ are allowed, format ans..40.

PayID

an32

ID assigned by Paygate for this transaction

Description of fields within the record for Batch files

The record area within the response file for Batch transactions looks the following way:

1
HEAD,<MerchantID>,<Date>,<Version>
2
EPS,Credit,<PayID>,<TransID>,(<RefNr>),<Amount>,<Currency>,<Status>,<Code>
3
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 <RefNR> and request parameters are returned unchanged and correspond to the call as specified before):

Key	Format	CND	Description
Action	a..20	M	The parameter Action defines the type of transaction: Credit
PayID	an32	M	ID assigned by Paygate for this transaction
Status	a..50	M	OK (URLSuccess) or FAILED (URLFailure)
Code	an8	M	Error code according to Paygate Response Codes (A4 Error codes)

Key

Format

CND

Description

Action

a..20

The parameter Action defines the type of transaction: Credit

PayID

an32

ID assigned by Paygate for this transaction

Status

a..50

OK (URLSuccess) or FAILED (URLFailure)

Code

an8

Error code according to Paygate Response Codes (A4 Error codes)

Description of result parameters within the record for Batch files