- Created by writer, last modified on 30. Sept 2021
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 7 Next »
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.
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 to receive Silent Order Post requests is referred to as PayNow.
<form action="../payNow.aspx" method="post">
This approach is very similar to 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.
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.
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.
PayNow
Silent Mode for credit cards with SSL and 3-D Secure method
PayNow links the benefits of Platform forms and Server-to-Server connections: As opposed to the Platform form, where the form is loaded from the Platform server by calling payssl.aspx, the PayNow form has to be provided by the merchant’s system. The form uses the same parameters as described here below.
In contrast to the Platform form, the parameters are not forwarded as URL parameters as is the case when calling the payssl.aspx, but as form input parameters. By the way for calling the PayNow.aspx the same parameters can be used as for PaySSL.aspx.
Please notice that in case of Fallback to 3-D Secure 1.0 the URLSuccess or URLFailure is called with GET. Therefore your systems should be able to receive parameters both via GET and via POST.
|
|
Sequence Diagram
Payment Request
The credit card data must be transmitted to paynow.aspx with the following parameters.
Please POST the form data as outlined in table below to payNow.aspx.
Form Elements
Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.
The table is being loaded. Please wait for a bit ...
Data Element | Legacy Element | 3DSV2 Element - Parameter from Card JSON Object | Description | Beschreibung |
---|---|---|---|---|
MerchantID | -- | -- | Merchant identifier assigned by | HändlerID, die von The page DE:Wording was not found -- Please check/update the page name used in the MultiExcerpt-Include macro vergeben wird |
Len | -- | -- | The length of the original encrypted with Blowfish | Die Länge des Originals verschlüsselt mit Blowfish |
Data | -- | -- | Blowfish encrypted data | Per Blowfish verschlüsselte Daten |
number | CCNr | number | Card number | Kartennummer |
securityCode | CCCVC | securityCode | Card security value | Kartenprüfnummer |
expiryDate | CCExpiry | expiryDate | Card expiry in format YYYYMM | Kartenablaufdatum im Format JJJJMM |
brand | CCBrand | brand | Card network | Kartensystem |
cardholder | CreditCardHolder | cardholderName | Name of the cardholder as printed on the card | Name des Karteninhabers, wie er auf der Karte gedruckt ist |
(-Â will continue to support the legacy form data fields that are currently in use. -)
Data
Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.
The table is being loaded. Please wait for a bit ...
Key | Format | CND | Description |
---|---|---|---|
ans..30 | M | MerchantID, assigned by . Additionally this parameter has to be passed in plain language too. |
Key | Format | CND | Description |
---|---|---|---|
TransID | ans..64 | M | TransactionID provided by you which should be unique for each payment |
Key | Format | CND | Description | Beschreibung |
---|---|---|---|---|
MsgVer | ans..5 | M | Message version. Accepted values:
| Message-Version. Zulässige Werte:
|
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 settlement file (CTSF) we cannot add the additional payment data. Notes:
| 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 The page DE:Wording was not found -- Please check/update the page name used in the MultiExcerpt-Include macro Settlement File (CTSF) auch nicht zusätzlich angereichert werden. |
Key | Format | CND | Description |
---|---|---|---|
Amount | n..10 | M | Amount in the smallest currency unit (e.g. EUR Cent). Please contact the , if you want to capture amounts <100 (smallest currency unit). |
Key | Format | CND | Description |
---|---|---|---|
Currency | a3 | M | Currency, three digits DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: Currency table |
Key | Format | CND | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Capture | an..6 | O | Determines the type and time of capture.
|
Key | Format | CND | Description | Beschreibung |
---|---|---|---|---|
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. | Ein auf dem Kontoauszug des Karteninhabers zu druckender Beschreiber. Beachten Sie bitte auch die andernorts gemachten zusätzlichen Hinweise für weitere Informationen über Regeln und Vorschriften. | |
OrderDesc | ans..768 | O | Order description | Beschreibung der Bestellung |
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:
| 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:
| |
JSON | O | Object specifying authentication policies and excemption handling strategies | Objekt, dass die Authentisierungs-Richtlinien und Strategien zur Behandlung von Ausnahmen angibt | |
JSON | O | Prior Transaction Authentication Information contains optional information about a 3DS cardholder authentication that occurred prior to the current transaction. | Das Objekt Prior Transaction Authentication Information enthält optionale Informationen über eine 3DS-Authentisierung eines Karteninhabers, die vor der aktuellen Transaktion erfolgt ist. | |
JSON | M | Accurate browser information are needed to deliver an optimized user experience. Required for 3DS 2.0 transactions. | Exakte Browserinformationen sind nötig, um eine optimierte Nutzererfahrung zu liefern. Erforderlich für 3DS 2.0 Transaktionen. | |
JSON | O | The account information contains optional information about the customer account with the merchant. | Die Kontoinformationen enthalten optionale Informationen über das Kundenkonto beim Händler. | |
JSON | C | The customer that is getting billed for the goods and / or services. Required unless market or regional mandate restricts sending this information. | Der Kunde, dem die Waren und / oder Dienstleistungen in Rechnung gestellt werden. Erforderlich, sofern nicht Markt- oder regionale Mandate das Senden dieser Informationen beschränken. | |
JSON | C | The customer that the goods and / or services are sent to. Required if different from billToCustomer. | Der Kunde, an den die Waren und / oder Dienstleistungen gesendet werden. Erforderlich, falls von billToCustomer abweichend. | |
JSON | C | Billing address. Required (if available) unless market or regional mandate restricts sending this information. | Rechnungsadresse. Erforderlich (falls verfügbar), sofern nicht Markt- oder regionale Mandate das Senden dieser Informationen beschränken. | |
JSON | C | Shipping address. If different from billingAddress, required (if available) unless market or regional mandate restricts sending this information. | Lieferadresse. Falls abweichend von billingAddress, erforderlich (falls verfügbar), sofern nicht Markt- oder regionale Mandate das Senden dieser Informationen beschränken. | |
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. | Objekt, dass Art und Reihe der Transaktionen angibt, die unter Verwendung von beim Händler hinterlegten Zahlungsdaten (z.B. Kontonummer oder Zahlungs-Token) zur Verarbeitung künftiger Käufe eines Kunden erfolgen. Erforderlich, falls zutreffend. | |
JSON | O | The Merchant Risk Indicator contains optional information about the specific purchase by the customer. If no | Der Händler-Risikoindikator enthält optionale Informationen über den bestimmten Einkauf des Kunden. Falls keine |
Key | Format | CND | Description |
---|---|---|---|
URLSuccess | ans..256 | M | Complete URL which calls up 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 and shop, please use the parameter UserData. Common notes:
|
Key | Format | CND | Description |
---|---|---|---|
URLFailure | ans..256 | M | Complete URL which calls up 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 and shop, please use the parameter UserData. Common notes:
|
Key | Format | CND | Description |
---|---|---|---|
URLNotify | ans..256 | M | Complete URL which 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. Common notes:
|
Key | Format | CND | Description |
---|---|---|---|
an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: |
Key | Format | CND | Description |
---|---|---|---|
UserData | ans..1024 | O | If specified at request, forwards the parameter with the payment result to the shop. |
Sample HTML Form
BASEURL=
<!DOCTYPE html> <html> <head> <title>Merchant Checkout</title> </head> <body> <form name="card form" action="BASEURLpayNow.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 completed 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.
HTTP POST to URLSuccess / URLFailure / URLNotify
Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.
The table is being loaded. Please wait for a bit ...
Key | Format | CND | Description |
---|---|---|---|
ans..30 | M | MerchantID, assigned by |
Key | Format | CND | Description | Beschreibung |
---|---|---|---|---|
MsgVer | ans..5 | M | Message version. Accepted values:
| Message-Version. Zulässige Werte:
|
Key | Format | CND | Description |
---|---|---|---|
PayID | an32 | M | ID assigned by for the payment, e.g. for referencing in batch files as well as for capture or credit request. |
Key | Format | CND | Description |
---|---|---|---|
XID | an32 | M | ID for all single transactions (authorisation, capture, credit note) for one payment assigned by |
Key | Format | CND | Description |
---|---|---|---|
TransID | ans..64 | M | TransactionID provided by you which should be unique for each payment |
Key | Format | CND | Description | Beschreibung |
---|---|---|---|---|
schemeReferenceID | ans..64 | C | Card scheme specific transaction ID required for subsequent credential-on-file payments, delayed authorizations and resubmssions | Kartensystemspezifische Transaktions-ID, die für nachfolgende Zahlungen mit hinterlegten Daten, verzögerte Autorisierungen und Wiedereinreichungen erforderlich ist |
Status | a..20 | M | Status of the transaction. Values accepted:
In case of Authentication-only the Status will be either | Status der Transaktion. Zulässige Werte:
Im Falle von nur Authentisierung ist der Status entweder |
Description | ans..1024 | M | Textual description of the code | Textliche Beschreibung des Codes |
Key | Format | CND | Description |
---|---|---|---|
Code | n8 | M | Error code according to Response Codes (A4 Response codes) |
Key | Format | CND | Description | Beschreibung |
---|---|---|---|---|
RefNr | an12 | M | 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 settlement file we cannot add the additional payment data. Notes:
| |
JSON | M | Card response data | Kartenantwortdaten | |
JSON | C | Object containing IP information. Presence depends on the configuration for the merchant. | Objekt mit IP-Informationen. Das Vorhandensein hängt von der Konfiguration des Händlers ab. | |
JSON | M | Authentication data | Authentisierungsdaten | |
JSON | C | In case the authentication process included a cardholder challenge additional information about the challenge result will be provided. | Falls der Authentisierungsprozess eine Challenge des Karteninhabers enthalten hat, werden zusätzliche Informationen über das Ergebnis der Challenge bereitgestellt |
Key | Format | CND | Description |
---|---|---|---|
UserData | ans..1024 | O | If specified at request, forwards the parameter with the payment result to the shop. |
Key | Format | CND | Description |
---|---|---|---|
an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: |
- No labels