Contents
About Trustly
General information about Trustly
Founded in 2008, Trustly is a technology enterprise from Sweden, which enables secure and convenient payments via online banking for the customers. Trustly offers Collecting as well as an automated credit (refund) via API and reconciliation files for all supported acquirers (all 21 main banks in Sweden, Denmark and Finland). Trustly is FSA regulated.
The Trustly online bank transfer is convenient for the customer and secure for the merchant. This payment method enables customers to be addressed who have an account at one of 30 banks in Sweden, Finland, Denmark and Spain. |
Process flow chart
Paygate interface
Data formats: 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) Abbreviations: 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
Trustly Online transfer
In order to make a payment with Trustly in Scandinavia, go to the following URL:
https://paymentpage.axepta.bnpparibas/trustly.aspx
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 Axepta BNP Paribas. Additionally this parameter has to be passed in plain language too. |
TransID | ans..64 | M | TransactionID which should be unique for each payment |
RefNr | ns..12 | M | Unique merchant reference number |
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 Only BAM, BGN, CZK, EEK, EUR, GBP, HRK, HUF, LTL, LVL, PLN, RON and USD permissible; the currency must match AddrCountryCode. |
MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm |
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. |
IPAddr | ans..15 | O | Customer´s IP address in IPv4 or IPv6 format |
FirstName | ans..100 | M | First name of the custumer |
LastName | ans..100 | M | Last name of the customer |
MobileNo | n..20 | O | Customer’s mobile telephone number |
CountryCode | a2 | O | Two characters country code according to ISO 3166 |
Language | ans..5 | O | Language, e.g. de_DE, en_US, sv_SE |
SocialSecurityNumber | ans..20 | O | Social security number, identity card number etc. |
CustomerId | ans..30 | O | Customer number |
URLTemplate | ans..256 | O | URL of your individual layout for the payment form. This template page can be self-designed but must be compliant to the security guidelins of Trustly. - all pictures need an absolute URL - all links must start with https - tags like script, iframe, frame, frameset, object, applet, etc are not allowed. The page must contain the following tag at any place. <!—TRUSTLY-PAYMENT-PAGE-GOES-HERE > At this place the Trustly transaction page (600x600px) will be displayed. |
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 |
RedirectURL | ans..256 | O | This parameter is mapped on the URLScheme on Truslty side (used for mobile app integration) |
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:
Parameter | Format | CND | Description | |
---|---|---|---|---|
MID | ans..30 | M | MerchantID, assigned by Axepta BNP Paribas | |
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, 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 document | |
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. | |
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 | |
Customer parameters (optional) | ||||
AccountId | ans..30 | O | Unique name/number to identify the specific customer account | |
Match | n1 | O | 0=not verified; 1=verified | |
AccClearingHouse | ans..50 | O | Clearing house for that account | |
AccOwner | ans..55 | O | Name of account holder | |
AccBank | ans..27 | O | Name of the bank | |
AccDescriptor | ans..100 | O | Additional text for identifying the customer | |
IBAN | n8 | O | Last digits of IBAN/ account number | |
UserId | ans..30 | O | Unique name/number for identifying the respective customers | |
AddrStreet | ans..100 | O | Customer’s street name and house number | |
AddrZip | ans..10 | O | Postcode of the customer | |
AddrCity | ans..30 | O | Town/city of the customer |
If “PendingNotify” is configured, only the standard parameters without the optional customer parameters are returned additionally to URLNotify.
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://paymentpage.axepta.bnpparibas/credit.aspx
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 BNP Paribas. Additionally this parameter has to be passed in plain language too. |
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 |
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 |
MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm |
The following table describes the Paygate response parameters:
Parameter | Format | CND | Description |
---|---|---|---|
MID | ans..30 | M | MerchantID, assigned by Axepta BNP Paribas |
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 |
MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm |
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 Trustly, which 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:
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) |
The structure for a Trustly payment within a Batch file to be submitted is as follows:
HEAD,<MerchantID>,<Date>,<Version> Trustly,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID> FOOT,<CountRecords>,<SumAmount> |
The following table describes the individual fields and values used within the data set (record) in the batch file:
Parameter | Format | CND | Description |
---|---|---|---|
Type | a..11 | M | HEAD for Header, FOOT for Footer, Trustly for Trustly |
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 | an12 | M | Unique reference number |
PayID | an32 | M | ID for this transaction given by Paygate |
The record area within the response file for Batch transactions looks as follows:
HEAD,<MerchantID>,<Date>,<Version> Trustly,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):
Parameter | Format | CND | Description |
---|---|---|---|
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 | Response code according to our platform Response Codes |