About Findomestic
General information about Findomestic
Further information can be found on the webpage of Findomestic (https://www.findomestic.it/).
Process flow chart
Authorisation (installment creation)
Capture (installment activation)
Cancel
Refund
Paygate interface
Format Description a alphabetical as alphabetical with special characters n numeric an alphanumeric ans alphanumeric with special characters ns numeric with special characters bool boolean expression (true or false) 3 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) Abbreviation Description CND condition M mandatory O optional C conditional Notice: Please note that the names of parameters can be returned in upper or lower case.Definitions
Data formats
Abbreviations
Comment If a parameter is mandatory, then it must be present If a parameter is optional, then it can be present, but it is not required If a parameter is conditional, then there is a conditional rule which specifies whether it is mandatory or optional
Authorisation (installment creation)
For installment creation please use the following URL:
Please note that after successful completion of instalment creation, the customer will need to upload additional documents on Findomestic portal. Findomestic will review the documents, send a contract to the customer in case of success, and the customer will need to sign the contract and upload it again on Findomestic portal. Only after completion of all these steps Findomestic will provide final decision about the instillment approval. It can take a couple of days.
In case positive response from Findomestic, Paygate will automatically activate the instalment on Findomestic side and send you notification about instalment approval/declining (refer to Activation).
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:
Parameter | Format | CND | Description |
|---|---|---|---|
MerchantID | ans..30 | M | MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too. |
TransID | ans..64 | M | Merchant transaction number, which must be unique |
RefNr | ans..30 | O | Unique reference number |
Amount | n..10 | M | Total order amount in the smallest currency unit (e.g. EUR Cent) incl. rebates and taxes (minimum amount: 100€). |
Currency | a3 | M | Currency, three digits DIN / ISO 4217 Only EUR permissible. |
OrderDesc | ans..768 | M | Description of goods and prices etc. |
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. |
UserData | ans..1024 | O | If specified at request, Paygate forwards the parameter with the payment result to the shop |
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. Please note that the Paygate must have a finalized transaction status for the first initial action. Submissions with identical ReqID for an open status will be processed regularly. |
| FirstName | ans..23 | O | First name |
| LastName | ans..23 | O | Last name |
| DateofBirth | ans10 | O | Date of birth in the format DD.MM.YYYY |
| ans..40 | O | Email address | |
| Label | ans..15 | O | When using this parameter your shop name will be displayed during application process. In order to avoid shortening of shop name („…“), please sumbit only about 1x 10 chars (or. 2x 10 chars with blank space between = line break). |
| MerchantIDExt | ans..30 | O | Program ID assigned to a merchant by Findomestic |
| Channel | ans..30 | O | Channel code assigned by Findomestic, default value B2C |
Custom | ans..1024 | 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 |
The following table describes the result parameters that the Paygate transmits to your URLSuccess, URLFailure or URLNotify. If you have specified the Response=encrypt parameter, the following parameters are sent Blowfish encrypted to your system:
Parameter | 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. |
XID | an32 | M | ID for all single transactions for one payment assigned by Paygate |
TransID | ans..64 | M | Merchant’s transaction number |
RefNr | ans..30 | O | Merchant’s unique reference number |
Status | a..30 | M | AUTHORIZE_REQUEST or FAILED |
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 | n8 | M | Error code according to Paygate Response Codes (A4 Error codes) |
MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm |
UserData | ans..1024 | O | If specified at request, Paygate forwards the parameter with the payment result to the shop |
| OrderDesc | ans..768 | O | Basket |
TransactionID | an..20 | M | Contract number with Consors |
| Duration | n..2 | M | Duration choosen by customer |
| InstallmentAmount | n..10 | M | Financing amount in the smallest currency unit (e.g. EUR Cent) |
Plain | ans..50 | O | A value to be set by the merchant to return some information unencrypted, e.g. the MID |
Custom | ans..1024 | 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 |
| IssuerInstallmentID | ans...32 | O | Issuer Installment ID generated by Findomestic |
| ApplicationID | ans...32 | O | Application ID generated by Findomestic |
Capture (installment activation)
After successful completion of Installment creation, the customer will need to upload additional documents on Findomestic portal. Findomestic will review the documents, send a contract to the customer in case of success, and the customer will need to sign the contract and upload it again on Findomestic portal. Only after completion of all these steps Findomestic will provide final decision about the instillment approval. It can take a couple of days.
In case positive response from Findomestic, Paygate will automatically activate the instalment on Findomestic side and send you notification about instalment approval/declining.
The following table describes the result parameters that the Paygate transmits to your URLNotify, specified on Installment creation, with information about Findomestic final decision about the installemnt.
Parameter | 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 |
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..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 | n8 | M | Error code according to Paygate Response Codes (A4 Error codes) |
RefNr | ans..30 | O | Merchant’s unique reference number |
| UserData | ans..1024 | O | If specified at request, Paygate forwards the parameter with the payment result to the shop |
Cancel
Reversals are possible via a Server-to-Server connection. If the instalment is still not finally approved by Findomestic, with this call you can reverse the complete instillment amount. Only full reversal is allowed, partial reversal possible is not possible. In case the instillment has been finally approved by Findomestic, Refund should be used.
In order to cancell a an installemnt with Findomestic, please use 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:
Parameter | Format | CND | Description |
|---|---|---|---|
MerchantID | ans..30 | M | MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too. |
PayID | an32 | M | ID assigned by Paygate for the payment to be reversed |
TransID | ans..64 | M | Merchant ID for the identification of the payment process to be reversed |
| RefNr | ans..30 | O | Merchant’s unique reference number |
Amount | n..10 | 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. Only MYR permissible. |
MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm |
| UserData | ans..1024 | O | If specified at request, Paygate forwards the parameter with the payment result to the shop |
| 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. Please note that the Paygate must have a finalized transaction status for the first initial action. Submissions with identical ReqID for an open status will be processed regularly. |
The following table describes the Paygate response parameters:
Parameter | 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 |
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..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 | n8 | M | Error code according to Paygate Response Codes (A4 Error codes) |
RefNr | ans..30 | O | Merchant’s unique reference number |
| UserData | ans..1024 | O | If specified at request, Paygate forwards the parameter with the payment result to the shop |
Refund
Reversals are possible via a Server-to-Server connection. If the instalment has been finally approved by Findomestic, with this call you can create a refund. Both full and partial refunds/multiple refunds are allowed. In case the instillment has not been finally approved by Findomestic, Reversal should be used.
Findomestic, please use 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:
Parameter | Format | CND | Description |
|---|---|---|---|
MerchantID | ans..30 | M | MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too. |
PayID | an32 | M | ID assigned by Paygate for the payment to be reversed |
TransID | ans..64 | M | Merchant ID for the identification of the payment process to be reversed |
| RefNr | ans..30 | O | Merchant’s unique reference number |
Amount | n..10 | 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. Only MYR permissible. |
MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm |
| UserData | ans..1024 | O | If specified at request, Paygate forwards the parameter with the payment result to the shop |
| 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. Please note that the Paygate must have a finalized transaction status for the first initial action. Submissions with identical ReqID for an open status will be processed regularly. |
The following table describes the Paygate response parameters:
Parameter | 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 |
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..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 | n8 | M | Error code according to Paygate Response Codes (A4 Error codes) |
RefNr | ans..30 | O | Merchant’s unique reference number |
| UserData | ans..1024 | O | If specified at request, Paygate forwards the parameter with the payment result to the shop |