Nexio mock gateway is only available in the Nexio sandbox and is for testing purposes. This section is intended to help you implement the Nexio mock gateway based on your preferred integration workflow.

Services and compatibility

Gateway-specific information

• Nexio mock gateway does not settle batches immediately. Transaction will automatically be settled at 05:00 UTC the following day from the transaction. For more information on how to manually settle, see Settling transactions manually below.
• Nexio mock gateway supports security code validation.
• Nexio mock gateway supports Address Verification Service.
• Nexio mock gateway support of void and refund includes card or echeck transactions.

Configuration

By default, the system automatically creates the following 3 paymentOptionTags for you to use with the Nexio mock gateway:

• nexio - For regular transactions.
• nexioAuto - For transactions that will auto settle.
• nexioAsync - For 3DS transactions.

To test out a transaction for the specific use case you have, add the value you want to the Run card transaction endpoint request in the processingOptions.paymentOptionTag parameter.

Required fields

There are no additional required fields.

Example requests

The following is an example Run card transaction request for Nexio mock gateway.

curl -X POST https://api.nexiopaysandbox.com/pay/v3/process \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -H 'Authorization: Basic [Base64_encoded_login]'
  -d '{
  "data": {
    "amount": 4.00,
    "surcharge": 1.50,
    "descriptor": {
    	"name": "Our Company Name",
			"address": "123 Main St.",
			"city": "New York City",
      "state": "NY",
      "postal": "10001",
      "country": "US",
      "phone": "1555555555",
      "url": "https://your-ecommerce-website.example.com",
      "merchantId": "1234",
      "mcc": "5964"
		}
  },
  "paymentMethod": "card",
  "tokenex": {
		"token": "eb50a022-d6de-4244-a1e6-dcb8522b2d19"
  }
}'

The following is an example Run echeck transaction request for Nexio mock gateway.

curl -X POST https://api.nexiopaysandbox.com/pay/v3/processECheck \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -H 'Authorization: Basic [Base64_encoded_login]'
  -d '{
  "data": {
    "amount": 4.00,
    "currency": "USD"
  },
  "tokenex": {
		"token": "eb50a022-d6de-4244-a1e6-dcb8522b2d19"
  }
}'

Testing data

Use the following test card information to test your Nexio mock gateway configuration.

Settling transactions manually

Although regular transactions will automatically settle at 05:00 UTC the following day from the transaction, if you would like to settle the transactions before the default time, you may do so manually by sending a POST request to the Settle Mock Gateway Payments endpoint:

POST https://api.nexiopaysandbox.com/mockGateway/v1/transactions/settle

Use Basic authentication for the request, and include the required merchantId parameter.

Required Parameters

merchantId - The merchant ID through which the mock transactions have been run.

{
    "merchantId": "100039"
}

curl -X POST https://api.nexiopaysandbox.com/mockGateway/v1/transactions/settle \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -H 'Authorization: Basic [Base64_encoded_login]'
  -d '{
    "merchantId": "100039"
}'

{
    "message": "success"
}

Status workflows

The status of a successful transaction with Nexio mock gateway varies, depending on the options you choose.

*Pending status displays as "authorized" or "AUTHORIZED" in the Nexio Dashboard; it displays as 10, meaning "authorized", in the response when querying transactions (for more information about transactionStatus, see the appropriate transactionStatus table).

If you have any additional questions or feedback, contact us.

See also

• Getting started with ecommerce
• 3D Secure overview
• Using a third-party 3DS provider to run transactions
• Sandbox environments
• Recurring billing overview