| Info | ||
|---|---|---|
| ||
|
...
- Create a test account with WorldPay
- Register for an account at https://developerengine.fisglobal.com
- Request Express Credentials at https://developerengine.fisglobal.com/apis/express/express-xml
- Review your established credentials at https://developerengine.fisglobal.com/dashboard
- As an alternate solution, you can use the following test credentials if you do not desire to set up a test account
data.accountID = "1217395";
data.accountToken = "C8E33719BEC41A4EA07B9E09681ED1323B9074E1651209203BE4C24452E884B4DD848601";
data.acceptorID = "364800780";
- Acquire appropriate test cards for testing transaction
- The demo server will reject non-approved test card numbers, so specific test cards must be used for approval testing
- To execute MasterCard and Visa test transactions for both Contact and Contactless: B2 Dual Interface EMV Test Card Set (6 cards)
- To execute test transactions for all four card brands for both Contact and Contactless: UAT USA EMV Test Card Set (21 cards)
- The demo server will reject non-approved test card numbers, so specific test cards must be used for approval testing
- Obtain a device with keys that work with the WorldPay test server. This must be a WorldPay Test Device
- The WorldPay Test Device must have a BDK 0123456789abcdeffedcba9876543210 and produce a KSN that starts with 6299491
- The WorldPay Production device will have a secret BDK and produce a KSN that starts with 9010500. This must only be used for live transactions
- Configure the device with the WorldPay configuration file (terminal settings, AIDs, CAPK) (requires Windows PC)
- Download the .json configuration file
- "Worldpay_Device_Config.json" → All devices Contact EMV
- "Worldpay_Device_Config_VP3300_CTLS.json" → VP3300/VP8300 Contact EMV with CTLS transactions enabled
- "Worldpay_Device_Config_VP3300_CTLS_ONLY.json" → VP3300/VP8300 Contactless ONLY
- Download and install "dot NET SDK Demo.zip"
- Run the utility, connect your device, and from the Command tree, select ViVOconfig→Set Config From File
- Load the file to your device
- Download the .json configuration file
- Download the demo application(s) for your platform(s). Refer to the source code and documentation with the downloads for implementation instructions.
- Run test transactions - Sale, Return, Void, Pre-Auth and Completion. Verify integration successful with POS application
- Establish a live merchant account
- Switch to a device with production keys on it that can properly encrypt data for the live server
- The WorldPay Production device will have a secret BDK and produce a KSN that starts with 9010500
- Configure the production device with the "Worldpay_Device_Config.json" or the "Worldpay_Device_Config_VP3300_CTLS.json" file as it was performed with the demo device
- Go live with payments (please refer to QuickStart guide)
...
- Create a test account with WorldPay
- Register for an account at https://developerengine.fisglobal.com
- Request Express Credentials at https://developerengine.fisglobal.com/apis/express/express-xml
- Review your established credentials at https://developerengine.fisglobal.com/dashboard
- As an alternate solution, you can use the following test credentials if you do not desire to set up a test account
AccountID = "1217395"
AccountToken = "C8E33719BEC41A4EA07B9E09681ED1323B9074E1651209203BE4C24452E884B4DD848601"
AcceptorID = "364800780"
License = "" (License not required for test transactions)
- On your web server, develop a solution that will collect and post to https://dev-paynow.itscocloud.com/execute the parameters required for executing a web based transaction. This could include, but not limited to:
- TransactionSetup: "1" = CreditCardSale
- ReturnURL: the web page that will receive the results from the transaction
- AutoReturn: "1" if the results are automatically returned to the ReturnURL, omit or set to "0" if results are displayed from WorldPay and another button is required to be clicked to execute the ReturnURL
- isTest: "1" if running test transactions, omit or set to "0" if running live transactions
- License: License number if isTest=0 (License required to perform live transactions)
- Credentials: Provide AccountID, AccountToken, AcceptorID (test or live, depending on "isTest")
- ReferenceNumber: Required unique value. Omit and a random value will be generated
- LaneNumber: Required value. Does not have to be unique
- TerminalID: Required value. Does not have to be unique
- Amount: Required value. Amount to charge.
- CVVRequired: "1" if CVV must be provided, omit or "0" if CVV is not required to be provided
- BillingAddress1: If AVS street address checking is desired, enter value for BillillingAddress1
- BillingZipCode: If AVS zip code checking is desired, enter a value for BillingZipCode
- After the transaction is executed, process the values returned to the "ReturnURL"
- Example Credit Card Sale transaction for $16.00, our test credentials, requiring CVV and will use AVS, with an auto-return url defined as the same hosted payment bridge:
- Sample response to above, when using Visa 4445222299990007, exp 12/22, CVV 382
- Review the QuickStart Guide for more details
- Review the Hosted Payments Test Cases for example transactions.
...