IDTECH Worldnay Hosted Payments Integration

तपशील

• Account Token: E1EB3EFB049DFB599F1CB454E1CFC4FD14BF90BCE74456AE9E9490D7D609B466C81A3801
• AcceptorID: 364798674
• AccountID: 1188346
• TransactionSetup: 1
• रक्कम: $16.00
• Billing Address: 100
• Billing Zipcode: 33606
• CVV Required: होय

ओव्हरview

हे दस्तऐवज होस्टेड पेमेंट एकत्रित करणाऱ्या डेव्हलपर्ससाठी मूलभूत माहिती प्रदान करते.

What are Hosted Payments?
Hosted Payments allows an existing merchant with WorldPay credentials AccountIDD, AccountToken, AcceptorID, ApplicationID) to enable their web server/e-commerce solution for payment acceptance by allowing the collection of manually-typed credit card information into a secure WorldPay-hosted page. This credit card information can then be processed for a Sale, a Pre-Auth, or it can be tokenized for future payment requests.

ID TECH Payment Bridge
To use Hosted Payments, WorldPay must first certify the solution. To enable ID TECH customers immediate access to Hosted Payments without requiring them to certify their own web solution, ID TECH has certified a Payment Bridge with WorldPay. ID TECH customers can utilize the payment bridge to execute certified Hosted Payment requests with WorldPay. This is accomplished by posting transaction requests to https://hpb.idtechproductscom/execute (https://uat.hpb.idtechproducts.com/execute for test transactions) with all required and optional parameters. The ID TECH Payment Bridge will then forward to WorldPay using certified logic. Requests can be made using NameValuePairs in the URL, किंवा बॉडीला JSON पॅकेट म्हणून फॉरमॅट करून आणि ते लक्ष्यावर पोस्ट करून URL.

व्यवहार पॅरामीटर्स

The following list is of all parameters that can be passed to the ID TECH Payment Bridge. These parameters are defined by WorldPay.

व्यवहार सेटअप प्रकार

द TransactionSetup parameter is required and can contain a valid value from 1–22. The types of transactions are as follows:

• CreditCardSale = 1
  • Credit Card Sale; requires रक्कम > 0.00.
• CreditCardAuthorization = 2
  • Credit Card Pre-Auth; requires रक्कम > 0.00.
• CreditCardAVSOnly = 3
  • AVS Check Only. Requires रक्कम = 0.00.
• PaymentAccountCreate = 7
  • Requests a payment token to be returned from the entered credit card info.
• PaymentAccountUpdate = 8
  • Updates a previous payment token.
• पूर्णता = १०
  • Completion from a previous pre-auth. Requires TransactionID.
• उलट = ११
  • Reversal from a previous transaction. Requires TransactionID.
• शून्यता = १२
  • Void from a previous transaction. Requires TransactionID.
• क्रेडिट = १३
  • Credit from a hard. Requires a credit card number.
• PaymentAccountCreateTransID = 14
  • Create a payment token from the previous transaction. Requires TransactionID.
• PaymentAccountQuery = 15
  • Query payment token.
• PaymentAccountRecordCount = 16
  • Payment token count.
• PaymentAccountRecordTokenReport = 17
  • Payment token report.
• PaymentAccountRecordDelete = 18
  • Delete payment token.
• PaymentAccountSale = 19
  • Perform a sale from a payment token.
• PaymentAccountAuthorization = 20
  • Perform a pre-auth from the payment token.
• परतफेड = २१
  • Refund from a previous transaction. Requires TransactionID.
• TransactionSetupQuery = 22
  • Query the status of a TransactionSetup. Requires TransactionSetupID.

विनंती स्वरूप: नाव मूल्य जोड्या (NVP)

The request format is as follows (UAT for test transactions)

The parameters should include, but not be limited to

The Return JRL must be defined as a page on the merchant web प्रतिसाद प्रक्रिया करणारी सेवा. प्रतिसाद खालीलप्रमाणे असेल.
?param1=val>&<param2=val>&…<paramX=val>

व्यवहार उदाampले: नाव मूल्य जोड्या (NVP)

Example Credit Card Sale transaction for 16,00, ID TECH test credentials, requiring CVV, and will use AVS, with an auto-return URL Google म्हणून परिभाषित. टीप: माजीample UAT वापरतो URL कारण हा एक चाचणी व्यवहार आहे.

Sample response to above, when using Visa exp 12/22, CVV 382

विनंती स्वरूप: JSON

The request format is as follows (using UAT for test transactions)

• चाचणी URL: https://uat.hpb.idtechproducts.com/execute
• लाइव्ह URL: https://mh.idtechproducts.com/execute

The parameters should include, but not be limited to

द रिटर्नURL must be defined as a page on the merchant’s web प्रतिसाद प्रक्रिया करणारी सेवा. प्रतिसाद एक JSON ऑब्जेक्ट असेल.

व्यवहार उदाampले: जेएसओएन
Example Credit Card Sale transaction $ 16.00, ID TECH test credentials, requiring CVV and will use AVS, with an auto-•return URL Google म्हणून परिभाषित. टीप: माजीample UAT वापरतो URL कारण हा एक चाचणी व्यवहार आहे.
चाचणी URL: (पोस्ट) https://uat.hpbidtechproductscom/execute

शरीर

विनंती a परत करते URL, You must redirect your browser to this URL, Exampप्रतिसाद

After the transaction is complete, the JSON response object will be returned to the ReturnlJRL specified in the request Example

Mobile Transaction Exampले: नाव मूल्य जोड्या (NVP)
For mobile transactions, we are not allowed to receive the ReturnJRL for the response. Instead, we need to poll the HBP for transaction status. When working with mobile transactions, we directly interact and process HTTP responses using web sockets. We do not utilize ReturnURL in this flow. We need to take note of the following parameters

• परतावेURL <NOT USED>
• AutoReturn <NOT USED>
• Embedded=l ->This will format the output for a mobile platform screen size
• OverrideRedirect-1 ->This will allow you to intercept the URL for the payments page

Example Credit Card Sale transaction $ 16.00, ID TECH test credentials, requiring CVV, and will use AVS. We want to format for mobile, and we want to intercept the URL. This must be sent as an http request through code, not in a web browser (HttpClient/HttpRequest or whatever Http framework is available on your platform).

विनंती a परत करते URL containing a TransactionSetupID to your HttpClient. You must present a mobile browser to the user in our mobile r redirect our browser to this URL. उदाampप्रतिसाद

While the user is viewing and interacting with the credit card entry web page, you will need to perform a TransactionSetupQuery(22) using the TransactionSetLWD from the URL. This request will return a record not found until the user finishes entering the credit card information, at which point it will return the transaction results. Continue to poll TransactionSetupQuery until transaction results are known. Example: Transaction Setup Query for TransactionSetupID. This must be sent as an http request through code, not in a web ब्राउझर

The request returns a query response to that TransactionSetupID. Example response when the transaction has not been completed yet.

If that TransactionSetupID has been completed with a successful transaction, you will get the results for that transaction. At this point,t you can direct your user to appropriate logic depending on the outcome of the transaction. Examine the response when the transaction has been completed.

Mobile Create Token Exampले: नाव मूल्य जोड्या (NVP)
When requesting to create a payment token from a credit card number (PaymentAccountCreate(7)), we are not allowed to receive the ReturnURL for the response. Instead, we need to poll the HBP for the token status. When working with mobile tokens, we directly interact and process HPB responses using web sockets. We do not utilize ReturnlJRL in this flow. We need to take note of the following parameters.

• ReturniJRL = <NOT USED>
• AutoReturn = <NOT USED>
• Embedded=l ->This will format the output for a mobile platform screen size
• OverrideRedirect=1 ->This will allow you to intercept the URL for the payments page

Example Payment Account Create, ID TECH test credentials. CVC is not available when creating a token. We want to format for mobile, and we want to intercept the URL. This must be sent as an http request through code, not in a web browser (HttpClient/HttpRequest or whatever Http framework is available on your platform., Required parameters: Amount-OOO and PaymentAccountReferenceNumber

विनंती a परत करते URL containing a TransactionSetupID to your HttpClient. You must present a mobile browser to the user in vour mobile app, redirect vour browser to this URL. उदाampप्रतिसाद

While the user is viewing and interacting with the credit card entry web page, you will need to perform a PaymentAccountQuery(15) using the TransactionSetupID from the URL. This request will return a record not found until the user finishes entering the credit card information, at which point it will return the token results. Continue to poll PaymentAccountQuery until token results are known. Example, Payment Account Query for TransactionSetupID. This must be sent as an http request through code, not in a web ब्राउझर

The request returns a query response to that TransactionSetupID. Example response when the transaction has not been completed

If that TransactionSetupID has been completed with a successful token creation, vou will get the results for that token. At this point, you can direct your user to the appropriate logic depending on the outcome of the token. Exam le res onse when the token has been created

वारंवार विचारले जाणारे प्रश्न

What should I do if my transaction fails?

In case of a failed transaction, double-check the entered information and try again. If the issue persists, contact customer support for assistance.

Is it safe to enter my CVV during the transaction?

Yes, entering your CVV is secure as it adds an extra layer of protection to your online transaction.

कागदपत्रे / संसाधने

IDTECH Worldnay Hosted Payments Integration [pdf] वापरकर्ता मार्गदर्शक Worldnay Hosted Payments Integration, Worldnay, Hosted Payments Integration, Integration

संदर्भ

• वापरकर्ता मॅन्युअल