• DeutschEnglish

SafeCharge

Logo

COO 6505 1000 13 2653229

Info

SafeCharge (a Nuvei company)

Type

Payments by Credit Card

Introduction

For more information about acquirers and connection, integration with Computop Paygate and Implementation of 3-D Secure (2.x), see chapter Card processing - common introduction.

Specific parameters for SafeCharge (Nuvei)

Besides the general parameters described below for the credit card connection, SafeCharge (Nuvei) requires the following additional parameters. An authorisation with 3-D Secure is possible.

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 additional encrypted payment request parameters described below for "interface via form" and "interface via Server-to-Server" :

Key

Format

CND

Description

RefNr

ns..30

O

Merchant’s unique reference number, which serves as payout reference in the acquirer EPA file. Please note, without the own shop reference delivery you cannot read out the EPA transaction and regarding the additional Computop settlement file (CTSF) we cannot add the additional payment data.

Only ASCII characters allowed, special characters ("Umlaute", diacritics) are not allowed and must be replaced by their ASCII-representation (e.g. ü → ue, é → e, ...).

UserData

ans..1024

O

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

RTF

a1

O

for repeat payments (subscriptions): I = Initial payment of a new subscription, R = Routine payment (Recurring)

CustomerID

an..20

O

Login name of the customer

ShopURL

an..128

O

URL of web page of the shop

sdState

a2

C

Code of Federal State in the delivery address. Mandatory only for card holders from USA and Canada

bdFirstName

an..30

O

First name of the customer

bdLastName

an..30

O

Last name of the customer

bdStreet

an..100

O

Customer’s address: Street name and house number

bdCity

an..40

O

Customer’s location

bdZIPCode

an..10

O

Postcode of the customer

bdCountryCode

an2

O

Country code of invoicing address according to ISO-3166-1, alphanumeric 2 chars

bdPhone

an..20

O

Customer’s phone number

bdEmail

ans..64

O

Email address of the customer

IPAddr

ans..15

O

Customer´s IP address for the transaction

MultiSettleCount

n..2

O

Relevant to VISA clearing message during authorisation. It represents the number of expected transactions in a multiple-settle Auth transaction.

channel

a4

O

Transaction type MOTO which supersedes the configured default value (ECOM).

User data (if available all parameters need to be enclosed)

Name

ans..100

C

User name of the customer

FirstName

ans..100

C

First name of the customer

LastName

ans..100

C

Last name of the customer

Email

ans..64

C

Email address of the customer

Language

a2

C

Language of the customer according to ISO, alphanumeric 2-digits

Delivery data (if available all parameters need to be enclosed)

sdFirstName

ans..100

C

First name in the delivery address

sdLastName

ans..100

C

Surname in the delivery address

sdStreet

ans..200

C

Street name in the delivery address

sdStreetNr

ans..5

C

Street number in the delivery address

sdZIPCode

an..20

C

Postcode in the delivery address

sdCity

ans..40

C

Town/city in the delivery address

sdState

a2

C

Code of Federal State in the delivery address

sdCountryCode

a2

C

Country code of delivery address according to ISO-3166-1, alphanumeric 2 chars

Address verification (AVS)

AddrStreet

ans..200

O

Street name (for AVS)

AddrZip

an..20

O

Postcode (for AVS)

AddrCountryCode

a2

O

Country code according to ISO-3166-1 alphanumeric (2-digits) (for AVS)

Additional parameters for credit card payments

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

these result parameters are additional to the standard parameters for "interface via form" and "interface via Server-to-Server" described below

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

RefNr

ns..30

O

Merchant’s unique reference number, which serves as payout reference in the acquirer EPA file. Please note, without the own shop reference delivery you cannot read out the EPA transaction and regarding the additional Computop settlement file (CTSF) we cannot add the additional payment data.

Only ASCII characters allowed, special characters ("Umlaute", diacritics) are not allowed and must be replaced by their ASCII-representation (e.g. ü → ue, é → e, ...).

UserData

ans..1024

O

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

CodeExt

n2

O

Extended response code from SafeCharge (Nuvei), if agreed with Computop Helpdesk

ErrorText

ans..255

O

Detailed SafeCharge (Nuvei) error message.

Is returned only if Status=FAILED, if agreed with Computop Helpdesk

Additional response parameters for credit card payments

Card processing - Credit Card Form

For more information about credit card processing via forms, please see chapter Credit Card Form (paySSL).

Card processing - Server-2-Server integration

For more information about credit card processing via server-to-server communication, please see chapter Server-2-Server Integration.

Capture / Credit / Reversal

For more information about capture, credit, reversal and credit card payment via POS terminals, please see chapter Card processing - Capture / Credit / Reversal / PayNow / Batch.

PayNow

For more information about PayNow, please see chapter Card processing - Capture / Credit / Reversal / PayNow / Batch.

Batch processing via the interface

For more information about batch processing, please see chapter Card processing - Capture / Credit / Reversal / PayNow / Batch.

Paygate

Documentation (EN)

Dokumentation (DE)

Paygate Status