Przelewy24 (via PPRO)

1. About Przelewy24 (via PPRO)

1.1 General information about Przelewy24

InfoTyp
Przelewy24 is an online banking method for Poland. It uses online bank authentication for account postings in real-time. Przelewy24 is supported by 18 large banks and reaches 95 % of the polish customers in online banking. The system has no transaction limit and directs customers via its online banking environment directly to the payment processing.Payments by Online Bank Transfer

1.2 Process flow chart

2 1cs Online Payment System-interface

2.1 Definitions

Data formats:

FormatDescription
aalphabetical
asalphabetical with special characters
nnumeric
analphanumeric
ansalphanumeric with special characters
nsnumeric with special characters
boolboolean expression (true or false)
3fixed length with 3 digits/characters
..3variable length with maximum 3 digits/characters
enumenumeration of allowed values
dttmISODateTime (YYYY-MM-DDThh:mm:ss)

Abbreviations:

AbbreviationDescriptionComment
CNDcondition
MmandatoryIf a parameter is mandatory, then it must be present
OoptionalIf a parameter is optional, then it can be present, but it is not required
CconditionalIf 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.

2.2 Payment with Przelewy24 via 1cs OPS form interface

To make a payment with Przelewy24 online transfer in Poland, please use the following URL:

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

Notice: For security reasons, 1cs Online Payment System 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:

KeyFormatCNDDescription
MerchantIDans..30MMerchantID, assigned by First Cash Solution. Additionally this parameter has to be passed in plain language too.
TransIDans..64M
TransactionID provided by you which should be unique for each payment
RefNrans..40OMerchant’s unique reference number. Only characters a-zA-Z0-9,-_ are allowed.
Amountn..10MAmount in the smallest currency unit (e.g. EUR Cent). Please contact the 1cs Support, if you want to capture amounts <100 (smallest currency unit).
Currencya3M
Currency, three digits DIN / ISO 4217, e.g. EUR, USD, GBP. Only PLN and EUR is permissible. Please find an overview here: Currency table
MACan64MHash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:
HMAC Authentication (Request)
HMAC Authentication (Notify)
OrderDescans..768MDescription of goods and prices. Intended purpose on the statement of account.
URLSuccessans..256MComplete URL which calls up 1cs Online Payment System 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 1cs Online Payment Systemand shop, please use the parameter UserData.
Common notes: We recommend to use parameter “response=encrypt” to get an encrypted response by 1cs OPS.
However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess. Therefore ensure to check the “code”-value which indicates success/failure of the action. Only a result of “code=00000000” should be considered successful.
URLFailureans..256M
Complete URL which calls up 1cs Online Payment System if payment has been unsuccessful. The URL may not be called up only via port 443. In order to exchange values between 1cs OPS and shop, please use the parameter User Data.
Common notes: We recommend to use parameter “response=encrypt” to get an encrypted response by 1cs OPS.
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.
Responsea7OStatus response sent by 1cs OPS to URLSuccess and URLFailure, should be encrypted. For this purpose, transmit Response=encrypt parameter.
URLNotifyans..256MComplete URL which 1cs OPS 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.
Common notes: We recommend to use parameter “response=encrypt” to get an encrypted response by 1cs OPS.
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.
UserDataans..1024OIf specified at request, 1cs OPS forwards the parameter with the payment result to the shop.
ReqIdans..32OTo 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, 1cs Online Payment System 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 1cs OPS 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 1cs OPS 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 1cs OPS.
SellingPointans..50OSelling point
Serviceans..50Oproducts or service sold
Channelans..64OConfiguration channel of the PPRO contract (account and ContractID are stored in the system). If it exists, it may overwrite channels stored in the system.
Languagea2O2-letter language code (e.g. de) that should be preferred when presenting payment pages to the consumer
AccOwnerans3..50MName of account holder
Emailans..100ME-Mail address of account holder
Plainans..50OA 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 1cs OPS and therefore protected against manipulation. 
Customans..1024O“Custom”-parameter is added to the request data before encryption and is part of encrypted “Data” in 1cs OPS request. By this they are protected against manipulation by a consumer. 
The Custom-value is added to the 1cs OPS 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 samples here: Custom
Parameters for payments with Przelewy24

The following table gives the result parameters which 1cs Online Payment System 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:

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

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

ParameterFormatCNDDescription
midans..30MMerchantID, assigned by the First Cash Solution
PayIDan32M
ID assigned by 1cs OPS for the payment, e.g. for referencing in batch files as well as for capture or credit request.
XIDan32MID for all single transactions (authorisation, capture, credit note) for one payment assigned by the 1cs OPS
TransIDans..64MTransactionID provided by you which should be unique for each payment
refnrans..40O
Merchant’s unique reference number. Only characters a-zA-Z0-9,-_ are allowed.
Statusa…50M
OK or AUTHORIZE_REQUEST (URLSuccess) as well as FAILED (URLFailure)
Descriptionans..1024MFurther details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis!
Coden8MError code according to 1cs OPS Response Codes (Error codes)
MACan64MHash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:
HMAC Authentication (Request)
HMAC Authentication (Notify)
UserDataans..1024OIf specified at request, 1cs OPS forwards the parameter with the payment result to the shop.
TIDan..40OTransaction reference at Przelewy24
PaymentPurposeans..26OPurpose of payment
PaymentGuaranteea..12OValue+ Description:
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.
ErrorTextans..128CDetailed PPRO error message.
Notice: Is returned only if Status=FAILED. Use is possible only in agreement with the First Cash Solution
TransactionIDan..20OUnique transaction number with PPRO
Plainans..50OA 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 the 1cs OPS and therefore protected against manipulation. 
Customans..1024O“Custom”-parameter is added to the request data before encryption and is part of encrypted “Data” in 1cs OPS request. By this they are protected against manipulation by a consumer. 
The Custom-value is added to 1cs OPS 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 samples here: Custom
Return parameters for URLSuccess, URLFailure and URLNotify with Przelewy24

2.3 Credit with reference

Credits (refunds) are possible via a Server-to-Server connection. For a Credit with reference to a capture 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, 1cs OPS 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:

ParameterFormatCNDDescription
MerchantIDans..30MMerchantID, assigned by the First Cash Solution. Additionally this parameter has to be passed in plain language too.
PayIDan32M
ID assigned by 1cs OPS for the payment to be credited
TransIDans..64MTransactionID provided by you which should be unique for each payment
Amountn..10MAmount in the smallest currency unit (e.g. EUR Cent). Please contact the First Cash Solution, if you want to capture amounts <100 (smallest currency unit).
Currencya3MCurrency, three digits DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: Currency table
MACan64MHash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:
HMAC Authentication (Request)
HMAC Authentication (Notify)
ReqIdans..32OTo 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, 1cs Online Payment System 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 1cs OPS 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 1cs OPS 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 1cs OPS.
Parameters for credit payments with Przelewy24 via socket connection

The following table describes the result parameters with which the 1cs OPS responds to your system

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

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

ParameterFormatCNDDescription
midans..30MMerchantID, assigned by the First Cash Solution
PayIDan32M
ID assigned by 1cs OPS for the payment, e.g. for referencing in batch files as well as for capture or credit request.
XIDan32MID for all single transactions (authorisation, capture, credit note) for one payment assigned by the 1cs OPS
TransIDans..64MTransactionID provided by you which should be unique for each payment
Statusa…50MOK or /URLSuccess) or FAILED (URLFailure)
Descriptionans..1024MFurther details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis!
Coden8MError code according to 1cs OPS Response Codes (Error codes)
refnrans..40OMerchant’s unique reference number. Only characters a-zA-Z0-9,-_ are allowed.
ErrorTextans..128CDetailed PPRO error message.
Notice: Is returned only if Status=FAILED. Use is possible only in agreement with the First Cash Solution
Response parameters for credit payments with Przelewy24 via socket connection

 

3. 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 within the data set (Record) for executing credits with Przelewy24 and which information can be found within the response file about the payment status.

Following table gives an overview of all batch versions that are possible for a specific action and their specialities:

ActionVersionDescription
Credit1.0 / 2.0Standard version without return of parameter Code
1.x / 2.xwith RefNr (valid for all versions other than 1.0)
Description of the possible batch versions

The structure for a Przelewy24 payment within a Batch file to be submitted is the following:

HEAD,<MerchantID>,<Date>,<Version>

Przelewy24,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>

FOOT,<CountRecords>,<SumAmount>

Example for Master MID function:

HEAD,[Master]MerchantID,Date,2.x

Type,Action,[Slave]MID,Amount,Currency,TransID,Data (depends on Action)

FOOT,CountRecords,SumAmount

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

KeyFormatCNDDescription
Typea..11MHEAD for Header, FOOT for Footer, Przelewy24 for Przelewy24
Actiona..20MThe parameter Action defines the type of transaction:
Credit
Amountn..10MAmount in the smallest currency unit (e.g. EUR Cent). Please contact the First Cash Solution, if you want to capture amounts <100 (smallest currency unit).
Currencya3MCurrency, three digits DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: Currency table
TransIDans..64MTransactionID provided by you which should be unique for each payment
RefNrans..40OMerchant’s unique reference number. Only characters a-zA-Z0-9,-_ are allowed.
PayIDan32MID assigned by 1cs OPS 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:

HEAD,<MerchantID>,<Date>,<Version>

Przelewy24,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<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 <RefNR> and request parameters are returned unchanged and correspond to the call as specified before):

KeyFormatCNDDescription
Actiona..20MThe parameter Action defines the type of transaction:
Credit
PayIDan32MID assigned by 1cs OPS for this transaction
Statusa..50MOK (URLSuccess) or FAILED (URLFailure)
Coden8MError code according to 1cs OPS Response Codes (Error codes)
Description of result parameters within the record for Batch files