About Paysafe Pay Later
General information about Paysafe Pay Later
| Logo |
|
|---|---|
| Info | With the products Purchase on invoice and Hire purchase merchants get tailored solutions for the region D-A-CH. Paysafe Pay Later especially features a fast and guaranteed payout as well as a comprehensive support for the B2B and B2C business. |
| Type | Payments by Invoice and Installments |
Further information can be found on the website of Paysafe Pay Later (https://www.paysafe.com).
Process flow chart
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
Paysafe Pay Later Invoice payment and Instalment payment
Paysafe Pay Later offers payment by instalment, on account or direct debit options. Different requests, which are controlled via the EventToken parameter, are necessary to completely finalise an authorisation.
Instalment payment:
- Instalment calculation (Calculation)
- Acceptance check before transaction (PreCheck)
- Authorization of the amount at transaction with disclosure of instalment term (PreAuthorization)
Purchase on account & direct debit:
- Acceptance check before transaction (PreCheck)
- Authorization of the amount at transaction (PreAuthorization)
There are further requests after authorisation which are carried out via the same URL:
- Re-authorization in order to change the amount before posting/dispatch. Not possible with payment by instalment. (ReAuthorization)
- Credit notification. Only possible after posting/dispatch. (RefundAnnouncements)
- Data completion only after subsequent disclosure of IDs. (AddData)
Dunning process
To trigger a dunning stop, the merchant has the option either via the portal provided by Paysafe Pay Later or by direct contact via email.
Creating/updating Paysafe Pay Later payments
In order to initialize a Paysafe Pay Later payment via server-to-server communication, please use the following URL:
https://www.computop-paygate.com/payolution.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:
Parameters for Paysafe Pay Later 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
Result parameters for Paysafe Pay Later payments
Capturing a Paysafe Pay Later payment
In order to capture a Paysafe Pay Later payment via a server-to-server communication, please use the following URL:
https://www.computop-paygate.com/capture.aspx |
Notice: A capture or partial capture is only possible for invoice payment. For instalment payment the capture is made automatically (Autocapture), so that a capture is not possible anymore.
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:
Parameters for capturing a Paysafe Pay Later payment
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
Response parameters for capturing a Paysafe Pay Later payment
Cancelling a Paysafe Pay Later authorization
In order to cancel a Paysafe Pay Later authorization via a server-to-server communication, please use the following URL:
https://www.computop-paygate.com/reverse.aspx |
Notice: A cancellation is only possible for invoice payment. For instalment payment the capture is made automatically (Autocapture), so that a cancellation is not possible anymore.
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:
Parameters for cancelling a Paysafe Pay Later payment
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
Response parameters for cancelling a Paysafe Pay Later payment
Crediting Paysafe Pay Later payments
In order to credit a Paysafe Pay Later payment via a server-to-server communication, 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:
Parameters for crediting a Paysafe Pay Later payment
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
Response parameters for crediting a Paysafe Pay Later payment
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 a Paysafe Pay Later capture or credit 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:
Description of the possible batch versions
The structure for a capture or credit within a Batch file to be submitted is the following:
HEAD,<MerchantID>,<Date>,<Version> Payolution,Capture,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID> Payolution,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
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> Payolution,Capture,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>,<Code> Payolution,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>,<Code> FOOT,<CountRecords>,<SumAmount>
Description of result parameters within the record for Batch files