Section

Column

width	900px

Column

width	900

Overview

A Silent Order Post or Direct Post is a transmission method where form data from a merchant website are getting directly posted to a third-party server. This is commonly achieved through the form action attribute that specifies the URL the data are sent to.

Info
Sensitive data such as card details can be captured within a merchant’s website without being processed by the merchant server as the POST is submitted silently. The URL endpoint in

...

Multiexcerpt include

SpaceWithExcerpt	EN
MultiExcerptName	Platform-Name
PageWithExcerpt	Wording

...

Computop Paygate to receive Silent Order Post requests is referred to as PayNow.

<form action="../payNow.aspx" method="post">

This approach is very similar to

...

Multiexcerpt include

SpaceWithExcerpt	EN
MultiExcerptName	Partner-Name
PageWithExcerpt	Wording

...

Computop hosted payment forms and leaves the merchant in full control of the checkout experience as all website elements are delivered from the merchant’s server.

Note

title	PCI-DSS Considerations

Merchants processing card transactions using the Silent Post model must submit the PCI DSS Self-Assessment Questionnaire (SAQ) A-EP. This SAQ is more comprehensive and thus might require more time and resources in comparison to SAQ A applicable to merchants that use hosted payment pages. However, merchants should always consult with their acquirer to evaluate the level of compliance required and refer to the PCI DSS guidelines. This does not affect the use of pseudo card numbers which is possible without submitting the SAQ questionaire.

Note

title	Notice about Cookie-/Session Handling

Please note that some browsers might block necessary cookies when returning to Your shop. Here you will find additial information and different solution approaches.

...

Table of Contents

...

Sequence Diagram

Image Modified

Payment Request

Please POST the form data as outlined in table below to

...

Multiexcerpt include

SpaceWithExcerpt	EN
MultiExcerptName	BaseURL
PageWithExcerpt	Wording

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

Form Elements

...

default	Beschreibung
isFirstTimeEnter	false
hideColumns	true
sparkName	Sparkline
hidePane	true
datepattern	dd M yy
id	1625494349836_-1514246176
worklog	365\|5\|8\|y w d h m\|y w d h m
isOR	AND
separator	Point (.)
order	0

...

MultiExcerptName	form_elements

...

	Data Element	Legacy Element	Description

...

1

MerchantID

--

Merchant identifier assigned by Computop.

...

SpaceWithExcerpt	EN
MultiExcerptName	Partner-Name
PageWithExcerpt	Wording

...

HändlerID, die von

Multiexcerpt include

SpaceWithExcerpt	DE
MultiExcerptName	Partner-Name
PageWithExcerpt	DE:Wording

vergeben wird

2

Len

--

The length of the original encrypted with Blowfish

...

.
3	Data	--	Blowfish encrypted data.

...

4

number

CCNr

Card number.

...

5

securityCode

CCCVC

Card security value.

...

6

expiryDate

CCExpiry

Card expiry in format YYYYMM.

...

7

brand

CCBrand

Card network.

...

8

cardholder

CreditCardHolder

...

.

Notice: Alphanumeric special characters, listed in EMV Book 4, “Appendix B”. Special characters have been added with EMV 3DS Version 2.3, but not all participants (banks) already support that standard.

Name

...

of the cardholder as printed on the card.

.

Hinweis: Alphanumerische Sonderzeichen gemäß EMV Book 4, „Anhang B“. Sonderzeichen wurden mit EMV 3DS Version 2.3 hinzugefügt, aber nicht alle Teilnehmer (Banken) unterstützen diesen Standard bereits.

(-

...

Multiexcerpt include

SpaceWithExcerpt	EN
MultiExcerptName	Partner-Name
PageWithExcerpt	Wording

...

Computop will continue to support the legacy form data fields that are currently in use. -)

Data

...

	Key

...

Format

...

Condition

...

Description

...

MultiExcerptName	data

...

dateFormat	dd M yy
export-word	false
show-source	false
export-csv	false
id	1625494349841_-1476467538
transpose	false
worklog	365\|5\|8\|y w d h m\|y w d h m
separator	.
export-pdf	false
sql	SELECT * FROM T*

Table Excerpt Include

static	true
name	MerchantID
page	MerchantID
type	page

Table Excerpt Include

static	true
name	TransID
page	TransID
type	page

...

1

...

MerchantID	ans..30	M	Merchant identifier assigned by Computop.
2

MsgVer

ans..5

M

Message version.

Accepted values:

2.0

...

Message-Version.

Zulässige Werte:

2.0


3	TransID	ans..64	M	Transaction identifier supplied by the merchant. Shall be unique for each payment.
4	RefNr	ans..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

...

Multiexcerpt include

SpaceWithExcerpt	EN
MultiExcerptName	Partner-Name
PageWithExcerpt	Wording

...

Computop settlement file (CTSF) we cannot add the additional payment data.

Details on supported format can be found below in payment specific section.

...

Eindeutige Referenznummer des Händlers, welche als Auszahlungsreferenz in der entsprechenden Acquirer EPA-Datei angegeben wird. Bitte beachten Sie, ohne die Übergabe einer eigenen Auszahlungsreferenz können Sie die EPA-Transaktionen nicht zuordnen, zusätzlich kann das

Multiexcerpt include

SpaceWithExcerpt	DE
MultiExcerptName	Partner-Name
PageWithExcerpt	DE:Wording

Settlement File (CTSF) auch nicht zusätzlich angereichert werden.

Informationen zum unterstützten Format finden Sie weiter unten in der zahlartspezifischen Beschreibung.

5	Amount	n..10	M	Transaction amount in it smallest unit of the submission currency.
6	Currency	a3	M	ISO 4217 three-letter currency code.
7	Capture	ans..6	O	Determines the type and time of payment completion (i.e. dual message systems). Values accepted: `AUTO` = completion immediately after authorisation (default value). `MANUAL` = completion made by the merchant. `<Number>` = Delay in hours until the completion (whole number; 1 to 696).
8

Table Excerpt Include

static	true
name	Amount
page	Amount
type	page

Table Excerpt Include

static	true
name	Currency
page	Currency
type	page

Table Excerpt Include

static	true
name	Capture
page	Capture
type	page

...

billingDescriptor

ans..22

O

A descriptor to be printed on a cardholder’s statement. Please also refer to the additional comments made elswhere for more information about rules and regulations.

...

9

OrderDesc

ans..768

O

Order description.

...

10

AccVerify

a3

O

Indicator to request an account verification (aka zero value authorization). If an account verification is requested the submitted amount will be optional and ignored for the actual payment transaction (e.g. authorization).

Values accepted:

Yes

...

Indikator zur Anforderung einer Konto-Verifizierung (alias Nullwert-Autorisierung). Wenn eine Konto-Verifizierung angefordert wird, ist der übermittelte Betrag optional und wird für die tatsächliche Zahlungstransaktion (d.h. Autorisierung) ignoriert.

Zulässige Werte:

Yes

11

threeDSPolicy

JSON

O

Object specifying authentication policies and excemption handling strategies

...

.
12	priorAuthenticationInfo	JSON	O	Prior Transaction Authentication Information contains optional information about a 3DS cardholder authentication that occurred prior to the current transaction.

...

13

browserInfo

JSON

M

Accurate browser information are needed to deliver an optimized user experience. Required for 3DS 2.0 transactions.

...

14

accountInfo

JSON

O

The account information contains optional information about the customer account with the merchant.

...

15

billToCustomer

JSON

C

The customer that is getting billed for the goods and / or services. Required unless market or regional mandate restricts sending this information.

...

16

shipToCustomer

JSON

C

The customer that the goods and / or services are sent to. Required if different from billToCustomer.

...

17

billingAddress

JSON

C

Billing address. Required (if available) unless market or regional mandate restricts sending this information.

...

18

shippingAddress

JSON

C

Shipping address. If different from billingAddress, required (if available) unless market or regional mandate restricts sending this information.

...

19

credentialOnFile

JSON

C

Object specifying type and series of transactions using payment account credentials (e.g. account number or payment token) that is stored by a merchant to process future purchases for a customer. Required if applicable.

...

20

merchantRiskIndicator

JSON

O

The Merchant Risk Indicator contains optional information about the specific purchase by the customer.

If no shippingAddress is present it is strongly recommended to populate the shippingAddressIndicator property with an appropriate value such as shipToBillingAddress, digitalGoods or noShipment.

...

Der Händler-Risikoindikator enthält optionale Informationen über den bestimmten Einkauf des Kunden.

Falls keine shippingAddress vorhanden ist, ist es dringend empfohlen, die Eigenschaft shippingAddressIndicator mit einem entsprechenden Wert wie shipToBillingAddress, digitalGoods oder noShipment auszufüllen.

Table Excerpt Include

static	true
name	URLSuccess
page	URLSuccess
type	page

Table Excerpt Include

static	true
name	URLFailure
page	URLFailure
type	page

Table Excerpt Include

static	true
name	URLNotify
page	URLNotify
type	page

Table Excerpt Include

static	true
name	MAC
page	MAC
type	page

Table Excerpt Include

static	true
name	UserData
page	UserData
type	page

Sample HTML Form

BASEURL=

Multiexcerpt include

SpaceWithExcerpt	EN
MultiExcerptName	BaseURL
PageWithExcerpt	Wording

...

MultiExcerptName	sample


21	URLNotify	an..256	M	A FQDN URL to submit the final payment result (HTTP POST).
22	URLSuccess	an..256	M	A FQDN URL for redirection of the client in case the payment could not be processed succefully (HTTP POST).
23	URLFailure	an..256	M	A FQDN URL for redirection of the client in case the payment could not be processed succefully (HTTP POST).
24	UserData	ans..1024	O	If specified at request, Paygate forwards the parameter with the payment result to the shop
25	MAC	an64	M	Hash Message Authentication Code (HMAC) with SHA-256 algorithm

Sample HTML Form

Code Block

language	xml
linenumbers	true

<!DOCTYPE html>
<html>
	<head>
		<title>Merchant Checkout</title>
	</head>
	<body>
		<form name="card form" action="

...

https://www.computop-paygate.com/payNow.aspx" method="post">
			<input type="hidden" name="MerchantID" value="MerchantID">
			<input type="hidden" name="Len" value="Length of the Blowfish encrypted data">
			<input type="hidden" name="Data" value="Blowfish encrypted data">
			Cardholder:
			<input type="text" name="cardholder"><br> 
			Card number:
			<input type="text" name="number"><br>
			Expiry date:
			<input type="text" name="expiryDate"><br>
			CVV2:
			<input type="text" name="securityCode"><br>
			Card brand:
			<input type="text" name="brand"><br>
			<input type="submit" value="Submit">
		</form>
	</body>
</html>

When the payment is

...

Multiexcerpt include

SpaceWithExcerpt	EN
MultiExcerptName	Platform-Name
PageWithExcerpt	Wording

...

completed Computop Paygate will send a notification to the merchant server (i.e. URLNotify) and redirect the browser to the URLSuccess resepctively to the URLFailure.

The blowfish encrypted data elements as listed in the following table are transferred via HTTP POST request method to the URLNotify and URLSuccess/URLFailure.

Note
Notice: Please note that the call of URLSuccess or URLFailure takes place with a GET in case of fallback to 3-D Secure 1.0. Therefore your systems should be able to receiver parameters both via GET and via POST.

HTTP POST to URLSuccess / URLFailure / URLNotify

...

	Key

...

Format

...

Condition

...

Description

...

MultiExcerptName	http_post

...

dateFormat	dd M yy
export-word	false
show-source	false
export-csv	false
id	1625494349844_1363819937
transpose	false
worklog	365\|5\|8\|y w d h m\|y w d h m
separator	.
export-pdf	false
sql	SELECT * FROM T*

Table Excerpt Include

static	true
name	MID
page	mid
type	page

...

1

...

MID	ans..30	M	Merchant identifier assigned by Computop.
2

MsgVer

ans..5

M

Message version.

Accepted values:

2.0

...

Message-Version.

Zulässige Werte:

2.0

3	PayID	ans32	M	Payment/transaction identifier assigned by Computop.
4	XID	ans64	M	ID assigned by Paygate for the operation performed on the payment.
5	TransID	ans..64	M	Transaction identifier supplied by the merchant. Shall be unique for each payment.
6

Table Excerpt Include

static	true
name	PayID
page	PayID
type	page

Table Excerpt Include

static	true
name	XID
page	XID
type	page

Table Excerpt Include

static	true
name	TransID
page	TransID
type	page

...

schemeReferenceID

ans..64

C

Card scheme specific transaction ID required for subsequent credential-on-file payments, delayed authorizations and resubmssions

...

.

7

...

Status

a..20

M

...

Staus of the transaction.

Values accepted:

Authorized
OK (Sale)
FAILED

In case of Authentication-only the Status will be either OK or FAILED.

...

Status der Transaktion.

Zulässige Werte:

Authorized
OK (Sale)
FAILED

Im Falle von nur Authentisierung ist der Status entweder OK oder FAILED.

...

8

Description

ans..1024

M

Textual description of the code.

...

9

Code

...

n8

...

M	Paygate response code.
10

...

card

JSON

M

Card response data.

...

11

...

ipInfo

JSON

C

Object containing IP information. Presence depends on the configuration for the merchant.

...

12	threeDSData

...

JSON

M

Authentication data.

...

13

...

resultsResponse

JSON

C

In case the authentication process included a cardholder challenge additional information about the challenge result will be provided.

...

14	UserData	ans..1024	C	If specified at request, Paygate forwards the parameter with the payment result to the shop
15	MAC	an64	M	Hash Message Authentication Code (HMAC) with SHA-256 algorithm
16	externalPaymentData	JSON	O	Optional additional data from acquirer/issuer/3rd party for authorization.

Column

Table Excerpt Include

static	true
name	UserData
page	UserData
type	page

...

Space shortcuts

Page tree

Versions Compared

Old Version 12

New Version 13

Key

Overview

Payment Request

Form Elements

Data

Sample HTML Form

Sample HTML Form

HTTP POST to URLSuccess / URLFailure / URLNotify

Paygate

Computop

Help

Intranet Tools

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 12

New Version 13

Key

Overview

Payment Request

Form Elements

Data

Sample HTML Form

Sample HTML Form

HTTP POST to URLSuccess / URLFailure / URLNotify