## Request parameters - asyncTraceId ## Response parameters - gatewayResponse - gatewayResponse.refNumber - gatewayResponse.gatewayName - history.processFromApi - history.processFromApi.initiatedAt - history.processFromApi.updatedAt - history.processFromApi.state - history.iframe - history.iframe.initiatedAt - history.iframe.updatedAt - history.iframe.state - history.popup - history.popup.initiatedAt - history.popup.updatedAt - history.popup.state - history.finale - history.finale.initiatedAt - history.finale.updatedAt - history.finale.state - updatedAt - initialTransactionStatus - createdAt - asyncTraceId
- [Save echeck token with iframe](https://docs.nexiopay.com/reference/saveechecktokeniframe-1.md): Returns an iframe that can be used to securely save a bank account information. For instructions on how to implement this endpoint, see [Creating a save echeck page with the iframe](doc:creating-a-save-echeck-page-with-the-iframe). For a tutorial about running a transaction with the saved echeck token, see the [Creating a card checkout page with the iframe](doc:creating-a-card-checkout-page-with-the-iframe), [Creating a card checkout page with your own form](doc:creating-a-card-checkout-page-with-your-own-form), or [Running a card transaction with the API](doc:running-a-card-transaction-with-the-api) topic. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must first request a [one-time-use token](ref:createonetimeusetoken). The system uses the processing and UI options sent in that request for the display and functionality of the iframe. ## Request parameters - shouldReturnHtml - token ## Response parameters - HTML form
- [Save echeck token](https://docs.nexiopay.com/reference/saveechecktoken-1.md): Allows you to securely save bank account information without a browser [using the API](doc:saving-an-echeck-token-with-the-api) or [using your own form](doc:creating-a-save-echeck-page-with-your-own-form). You may save a new e-check by including the `card` object or add existing TokenEx echeck token for use in Nexio by including the `token` object. Echeck tokens can be used to process through any MID on your account. They are not restricted to a specific merchant account or currency. > ๐ Note > > Processing options must be sent in the request for a [one-time-use token](ref:createonetimeusetoken). For more information, see [What data is saved with tokens?](doc:what-data-is-saved-with-tokens) in Guides. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - bank - bank.accountHolderName - bank.routingNumber - bank.encryptedBankAccountNumber - token - data - data.customer - data.customer.billToAddressOne - data.customer.billToAddressTwo - data.customer.billToCity - data.customer.billToCountry - data.customer.billToPhone - data.customer.billToPostal - data.customer.billToState - data.customer.companyName - data.customer.createdAtDate - data.customer.email - data.customer.firstName - data.customer.invoice - data.customer.lastName - data.customer.orderNumber - data.customer.phone - data.customer.shipToAddressOne - data.customer.shipToAddressTwo - data.customer.shipToCity - data.customer.shipToCountry - data.customer.shipToPhone - data.customer.shipToPostal - data.customer.shipToState - data.customFields - data.customFields.exampleKey - tokenex - tokenex.token - tokenex.lastFour ## Response parameters - token - token.token - tokenx.lastFour - data - data.customer - data.customer.billToAddressOne - data.customer.billToAddressTwo - data.customer.billToCity - data.customer.billToCountry - data.customer.billToPhone - data.customer.billToPostal - data.customer.billToState - data.customer.companyName - data.customer.email - data.customer.firstName - data.customer.lastName - data.customer.phone - data.customer.shipToAddressOne - data.customer.shipToAddressTwo - data.customer.shipToCity - data.customer.shipToCountry - data.customer.shipToPhone - data.customer.shipToPostal - data.customer.shipToState - bank - bank.accountHolderName - bank.routingNumber - merchantId
- [Run echeck transaction with iframe](https://docs.nexiopay.com/reference/runechecktransactioniframe-1.md): Returns an iframe that can be used to securely process an echeck transaction. For instructions on how to implement this endpoint, see the [Creating an echeck checkout page with the iframe](doc:creating-an-echeck-checkout-page-with-the-iframe) topic. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must first request a [one-time-use token](ref:createonetimeusetoken). The system uses the processing and UI options sent in the request for the creation of the one-time-use or saved echeck token in the display and functionality of the iframe. ## Request parameters - shouldReturnHtml - token ## Response parameters - HTML form
- [Run echeck transaction](https://docs.nexiopay.com/reference/runechecktransaction-1.md): Allows you to process an echeck transaction in any of the following situations: - An initial transaction that uses a saved echeck token. - A subsequent transaction that uses a saved echeck token. For more information about how to implement this endpoint, see the [Creating an echeck checkout page with your own form](doc:creating-an-echeck-checkout-page-with-your-own-form) or [Running an echeck transaction with the API](doc:running-an-echeck-transaction-with-the-api) topic. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - data - data.amount - data.currency - data.cart - data.cart.items - data.cart.items.item - data.cart.items.description - data.cart.items.quantity - data.cart.items.price - data.cart.items.type - data.customer - data.customer.billToAddressOne - data.customer.billToAddressTwo - data.customer.billToCity - data.customer.billToCountry - data.customer.billToPhone - data.customer.billToPostal - data.customer.billToState - data.customer.companyName - data.customer.createdAtDate - data.customer.customerRef - data.customer.email - data.customer.firstName - data.customer.invoice - data.customer.lastName - data.customer.orderNumber - data.customer.phone - data.customer.shipToAddressOne - data.customer.shipToAddressTwo - data.customer.shipToCity - data.customer.shipToCountry - data.customer.shipToPhone - data.customer.shipToPostal - data.customer.shipToState - data.customFields - data.customFields.exampleKey - secCode - settlementCurrency - tokenex - tokenex.token - tokenex.customerRefNumber - tokenex.lastFour - bank - bank.accountHolderName - bank.routingNumber - processingOptions - processingOptions.verboseResponse - processingOptions.merchantId ## Response parameters - amount - authCode - bank - bank.accountHolderName - bank.routingNumber - bank.accountNumber - currency - data - data.amount - data.cart - data.cart.items - data.cart.items.item - data.cart.items.description - data.cart.items.quantity - data.cart.items.price - data.cart.items.type - data.currency - data.customFields - data.customFields.exampleKey - data.customer - data.customer.billToAddressOne - data.customer.billToAddressTwo - data.customer.billToCity - data.customer.billToCountry - data.customer.billToPhone - data.customer.billToPostal - data.customer.billToState - data.customer.companyName - data.customer.createdAtDate - data.customer.customerRef - data.customer.email - data.customer.firstName - data.customer.invoice - data.customer.lastName - data.customer.orderNumber - data.customer.phone - data.customer.shipToAddressOne - data.customer.shipToAddressTwo - data.customer.shipToCity - data.customer.shipToCountry - data.customer.shipToPhone - data.customer.shipToPostal - data.customer.shipToState - data.lodging - data.lodging.advanceDeposit - data.lodging.checkInDate - data.lodging.checkOutDate - data.lodging.noShow - data.lodging.roomNumber - data.lodging.roomRate - data.settlementCurrency - gatewayResponse - gatewayResponse.gatewayName - gatewayResponse.refNumber - id - merchantId - transactionDate - transactionStatus - transactionType
- [View currency conversion rates](https://docs.nexiopay.com/reference/conversionrates-1.md): > transaction. ## Request parameters - id - data - data.amount ## Response parameters - amount - authCode - currency - data - data.amount - data.currency - data.settlementCurrency - gatewayResponse - gatewayResponse.gatewayName - gatewayResponse.refNumber - id - merchantId - message - transactionDate - transactionStatus - transactionType
- [Void a transaction](https://docs.nexiopay.com/reference/voidtransaction-1.md): Allows you to void a credit card, debit card, or echeck transaction using the Nexio Payment ID. In order to void a transaction, it must have been authorized but not yet settled. The entire process for voiding a transaction is as follows: 1. A transaction using the [Run card transaction](ref:runcardtransaction) or [Run echeck transaction](ref:runechecktransaction) endpoint occurs. 2. Retrieve the `id` from the response. This is the Nexio Payment ID. 3. Include that `id` in the body of your request for this endpoint in order to void the transaction. If you do not know the `paymentId`, you can get an array of possible transactions that have authorized but are not yet settled with the [View transactions](ref:viewtransactions) endpoint and at least the following query filters:
`transactionStatus=10`
`plugin=` > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include the ID as indicated above. ## Request parameters - id ## Response parameters - id - merchantId - transactionDate - authCode - transactionStatus - transactionType - currency - message - data - data.currency - data.settlementCurrency - gatewayResponse - gatewayResponse.gatewayName - gatewayResponse.refNumber
- [Refund a transaction](https://docs.nexiopay.com/reference/refundtransaction-1.md): Allows you to refund all or part of a previous credit card, debit card, or echeck transaction using the Nexio Payment ID. In order to refund a transaction, it must have already settled. The entire process for refunding a transaction is as follows: 1. Run a transaction using the [Run card transaction](ref:runcardtransaction) or [Run echeck transaction](ref:runechecktransaction) endpoint. 2. Retrieve the `id` from the response. This is the Nexio Payment ID. 3. Use the dashboard from the gateway connection that processed the transaction to manually settle the transaction if that is possible (or wait for the transaction to settle). Note that you can use the [Nexio mock gateway](doc:nexio-mock-gateway-integration-guide) and the `paymentOptionTag` of `nexioAuto` to immediately make a transaction settle. 4. Include the payment `id` in the body of your request for this endpoint, along with an `amount` that is less than or equal to the original transaction amount. Note that some gateway connections allow multiple refunds per transaction. In this situation, you should ensure that the total of all refunds does not exceed the amount charged in the original transaction. If you do not know the `paymentId` or the maximum `amount` to refund, you can get an array of possible transactions that have settled with the [View transactions](ref:viewtransactions) endpoint and at least the following query filters:
`transactionStatus=20`
`plugin=` > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include the ID and a refund amount, as indicated above. You may also include a description of why you are issuing the refund. ## Request parameters - id - data - data.amount - refundReason ## Response parameters - id - merchantId - transactionDate - authCode - transactionStatus - transactionType - currency - amount - message - data - data.currency - data.settlementCurrency - data.amount - gatewayResponse - gatewayResponse.gatewayName - gatewayResponse.refNumber - recurringData - recurringData.recurringId - recurringData.recurringIdType
- [View card tokens](https://docs.nexiopay.com/reference/viewcardtokens-1.md): Allows you to view all saved card tokens based on the given criteria. > ๐ Note > > Nexio does not currently support returning terminal tokens from this endpoint. Instead, use the terminal's token with the [View card token details](ref:viewcardtokendetails) endpoint. Saved card tokens can be used to process through any MID on your account. They are not restricted to a specific merchant account or currency. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments). > > You can include any of the possible filters, or none of them, in your request. For example, `/card/v3/?expirationYear<2024&merchantId=000999` to return all records for the given merchantId and a card expiration year before 2024. ## Request parameters - limit - offset - createdAt - updatedAt - merchantId - merchantIds - customerRef - expirationMonth - expirationYear - accountUpdaterStatus - shouldUpdateCard - lastAccountUpdaterUpdate - pauseAccountUpdater - cardType - firstSix - lastFour - token - cardHolderName ## Response parameters - limit - offset - hasMore - rows.key - rows.merchantId - rows.customerRef - rows.expirationMonth - rows.expirationYear - rows.accountUpdaterStatus - rows.shouldUpdateCard - rows.lastAccountUpdaterUpdate - rows.pauseAccountUpdater - rows.createdAt - rows.updatedAt - rows.cardType - rows.firstSix - rows.lastFour - rows.token - rows.cardHolderName - random-nnnn
- [View card token details](https://docs.nexiopay.com/reference/viewcardtokendetails-1.md): Allows you to view details of a specific card or terminal token. Card tokens can be used to process through any MID on your account. They are not restricted to a specific merchant account or currency. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include a saved card token in the path parameter of the request. (Due to technical limitations, the **Try It** feature does not support the use of a terminal token.) ## Request parameters - cardToken ## Response parameters - accountUpdaterStatus - card.expirationMonth - card.expirationYear - card.cardHolderName - card.firstSix - card.lastFour - card.token - card.cardType - data - data.customer - data.customer.billToAddressOne - data.customer.billToAddressTwo - data.customer.billToCity - data.customer.billToCountry - data.customer.billToPhone - data.customer.billToPostal - data.customer.billToState - data.customer.birthDate - data.customer.createdAtDate - data.customer.customerRef - data.customer.email - data.customer.firstName - data.customer.invoice - data.customer.lastName - data.customer.phone - data.customer.shipToAddressOne - data.customer.shipToAddressTwo - data.customer.shipToCity - data.customer.shipToCountry - data.customer.shipToPhone - data.customer.shipToPostal - data.customer.shipToState - dateCreated - dateLastModified - merchantId - shouldUpdateCard - tokenex - tokenex.cardType - tokenex.firstSix - tokenex.lastFour - tokenex.token
- [Update card token](https://docs.nexiopay.com/reference/updatecardtoken-1.md): Allows you to edit the card information, account updater status, and customer information for an existing card or terminal token. To get the current card information for a token, see the [View card tokens](ref:viewcardtokens) or [View card token details](ref:viewcardtokendetails) endpoints. > ๐ Note > > - Card tokens can be used to process through any MID on your account. They are not restricted to a specific merchant account or currency. > - Use this endpoint to register/deregister card tokens with the account updater service. > - Cards registered with the account updater service may take up to 72 hours to be deregistered. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include a saved card or terminal token in the path parameter of the request, along with the new token information in the body of the request. (Due to technical limitations, the **Try It** feature does not support the use of a terminal token.) ## Request parameters - cardToken - card - card.expirationMonth - card.expirationYear - card.cardHolderName - card.cardType - card.firstSix - card.lastFour - data - data.customer - data.customer.billToAddressOne - data.customer.billToAddressTwo - data.customer.billToCity - data.customer.billToCountry - data.customer.billToPhone - data.customer.billToPostal - data.customer.billToState - data.customer.birthDate - data.customer.customerRef - data.customer.email - data.customer.firstName - data.customer.lastName - data.customer.phone - data.customer.shipToAddressOne - data.customer.shipToAddressTwo - data.customer.shipToCity - data.customer.shipToCountry - data.customer.shipToPhone - data.customer.shipToPostal - data.customer.shipToState - shouldUpdateCard ## Response parameters - accountUpdaterStatus - dateCreated - dateLastModified - merchantId - shouldUpdateCard - currencyCode - card - card.expirationMonth - card.expirationYear - card.cardHolderName - card.cardType - card.cardNumber - card.firstSix - card.lastFour - data - data.customer - data.customer.customerRef - data.customer.birthDate - data.customer.email - data.customer.firstName - data.customer.lastName - data.customer.phone - data.customer.billToAddressOne - data.customer.billToAddressTwo - data.customer.billToCity - data.customer.billToState - data.customer.billToPostal - data.customer.billToCountry - data.customer.billToPhone - data.customer.shipToAddressOne - data.customer.shipToAddressTwo - data.customer.shipToCity - data.customer.shipToState - data.customer.shipToPostal - data.customer.shipToCountry - data.customer.shipToPhone - tokenex - tokenex.cardType - tokenex.firstSix - tokenex.lastFour - tokenex.token - originalCard - originalCard.cardHolderName - originalCard.expirationMonth - originalCard.expirationYear
- [Delete card tokens](https://docs.nexiopay.com/reference/deletecardtokens-1.md): Allows you to delete card or terminal tokens from the card vault. > ๐ Note > > Cards registered with the account updater service may take up to 72 hours to be removed. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include an array of one or more existing card or terminal tokens in the body of the request. ## Request parameters - tokens ## Response parameters - key - message - status - error - error.0 - error.0.message - error.0.tableName - error.1 - error.1.message - error.1.cardError
- [View echeck token details](https://docs.nexiopay.com/reference/viewechecktokendetails-1.md): Allows you to view details of a specific echeck token. Echeck tokens can be used to process through any MID on your account. They are not restricted to a specific merchant account or currency. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include a saved echeck token in the path parameter of the request. ## Request parameters - echeckToken ## Response parameters - bank - bank.accountHolderName - bank.routingNumber - tokenex - tokenex.lastFour - tokenex.token - data - data.customer - data.customer.orderNumber - data.customer.invoice - data.customer.customerRef - data.customer.companyName - data.customer.firstName - data.customer.lastName - data.customer.birthDate - data.customer.email - data.customer.phone - data.customer.billToAddressOne - data.customer.billToAddressTwo - data.customer.billToCity - data.customer.billToState - data.customer.billToPostal - data.customer.billToCountry - data.customer.billToPhone - data.customer.shipToAddressOne - data.customer.shipToAddressTwo - data.customer.shipToCity - data.customer.shipToState - data.customer.shipToPostal - data.customer.shipToCountry - data.customer.shipToPhone - dateCreated - dateLastModified - merchantId
- [Create simple login](https://docs.nexiopay.com/reference/createsimplelogin.md): Simple Login allows trusted users to proceed directly to the retail/MOTO iframe without entering a Nexio username and password. This option is useful for cases in which multiple users will be using a single Nexio account. It can also save time for internal users by eliminating the need to enter a username and password upon each use. Use the `key` value from the response as a query parameter in the request to load Nexio's retail iframe. For additional information about using this endpoint, see the [Using simple login for authentication](doc:using-simple-login-for-authentication) tutorial. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments) that you want to use for transactions and other tasks with the retail iframe. ## Response parameters - exp - jwt - key - refreshToken - username
- [View terminal list](https://docs.nexiopay.com/reference/viewterminallist.md): Retrieves a list of available terminals. You use the `terminalId` from this response in order to send a POST request to the [Process transaction from terminal](ref:processtransactionfromterminal) endpoint. > ๐ Note > > Terminals must be configured before they are available for processing. Depending on the terminal and your merchant account configuration, you need to either [pair the terminal](ref:pairterminal) or [register the terminal](ref:registerterminal). For additional information about this process, see the [Getting started with retail](doc:getting-started-with-retail) topic in Guides. > > If you do not see your terminal in the list retrieved through this endpoint, contact [Integrations Support](page:contact-us) for assistance. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Response parameters - gatewayLabel - gatewayName - gatewayType - merchantId - merchantName - terminalId - terminalName - terminalSerialNumber - terminalKey - terminalStatus
- [Process transaction from terminal](https://docs.nexiopay.com/reference/processtransactionfromterminal.md): Initiates a transaction through a terminal through the Nexio API rather than using the retail iframe. For more information on how to use this endpoint, see the steps in [Processing a transaction with a terminal](doc:processing-a-transaction-with-a-terminal) in Guides. You can also specify to save the card token from the terminal transaction so that you can use it for future transactions (through the [Run card transaction](ref:runcardtransaction) endpoint). > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). > > You must also have a terminal connected to the Nexio account. For more information, see the [Pair terminal](ref:pairterminal) or [Register terminal](ref:registerterminal) endpoints. ## Request parameters - data - data.amount - data.currency - data.customFields - data.customer - data.customer.customerRef - data.customer.orderNumber - data.customer.orderDate - data.customer.invoice - data.customer.firstName - data.customer.lastName - data.customer.birthDate - data.customer.nationalIdentificationNumber - data.customer.email - data.customer.phone - data.customer.billToAddressOne - data.customer.billToAddressTwo - data.customer.billToCity - data.customer.billToState - data.customer.billToPostal - data.customer.billToCountry - data.customer.billToPhone - data.customer.shipToAddressOne - data.customer.shipToAddressTwo - data.customer.shipToCity - data.customer.shipToState - data.customer.shipToPostal - data.customer.shipToCountry - data.customer.shipToPhone - data.description - data.lodging - data.lodging.advanceDeposit - data.lodging.checkInDate - data.lodging.checkOutDate - data.lodging.noShow - data.lodging.roomNumber - data.lodging.roomRate - terminalId - processingOptions.saveCardToken - isAuthOnly - card - card.cardHolderName ## Response parameters - terminalRequestId - terminalRequestStatus
- [View terminal transaction status](https://docs.nexiopay.com/reference/viewterminaltransactionstatus.md): Checks the status of a transaction run through a terminal. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - terminalRequestId ## Response parameters - gatewayResponse - gatewayResponse.gatewayName - currency - transactionStatus - terminal.token - terminalRequestId - authCode - transactionType - card - card.cardType - card.cardHolder - card.cardNumber - card.firstSix - card.lastFour - card.expirationMonth - card.expirationYear - processingOptions - processingOptions.merchantId - terminalRequestStatus - data - data.description - data.amount - data.currency - data.cart - data.cart.items - data.cart.items.item - data.cart.items.description - data.cart.items.quantity - data.cart.items.price - data.cart.items.type - data.customFields - data.customFields.exampleKey - data.customer - data.customer.firstName - data.customer.lastName - data.customer.customerRef - data.customer.orderNumber - data.customer.invoice - data.customer.email - data.customer.phone - data.customer.billToPhone - data.customer.billToAddressOne - data.customer.billToAddressTwo - data.customer.billToCity - data.customer.billToState - data.customer.billToPostal - data.customer.billToCountry - data.customer.shipToPhone - data.customer.shipToAddressOne - data.customer.shipToAddressTwo - data.customer.shipToCity - data.customer.shipToState - data.customer.shipToPostal - data.customer.shipToCountry - data.lodging - data.lodging.advanceDeposit - data.lodging.checkInDate - data.lodging.checkOutDate - data.lodging.noShow - data.lodging.roomNumber - data.lodging.roomRate - amount - transactionDate - id (this is the paymentId)
- [Pair terminal](https://docs.nexiopay.com/reference/pairterminal.md): Initiates pairing with a terminal. Depending on the merchant account configuration, when you add a terminal, you either need to request a pairing code or [add a registration code](ref:registerterminal). Some accounts may be configured to do both terminal setup options if the account is configured with multiple eligible gateways. For more information on how to pair a terminal, see [Pairing the terminal](doc:configuring-your-terminal-for-usaepay#pairing-the-terminal) in Guides. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - merchantId - terminalName ## Response parameters - terminalName - pairingCode - expirationDate - key
- [Register terminal](https://docs.nexiopay.com/reference/registerterminal.md): Provides a registration (or activation) code from a terminal to Nexio's API in order to register the terminal with the appropriate gateway. Depending on the merchant account configuration, when you add a terminal, you either need to add a registration code or [request a pairing code](ref:pairterminal). Some accounts may be configured to do both terminal setup options if the account is configured with multiple eligible gateways. If you are unsure which endpoint to use, please contact [Support](https://docs.nexiopay.com/page/contact-us). For a tutorial on how to use this endpoint, see the [Registering and deregistering terminals](doc:registering-and-deregistering-terminals) topic in **Guides**. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments) and you must have an account with a gateway that requires terminal registration. ## Request parameters - merchantId - terminalRegistrationCode - terminalName ## Response parameters - terminalName - deviceId - terminalSerialNumber - terminalRegistrationStatus - terminalId
- [Deregister terminal](https://docs.nexiopay.com/reference/deregisterterminal.md): Removes a terminal's registration through the Nexio API. > ๐ Notes > > - In addition to this API, you can deregister a terminal directly within the gateway user interface. > - You can only deregister terminals that have already been [registered](ref:registerterminal) with Nexio. > - You may need to deregister a terminal in situations such as when the terminal needs to be used with a different gateway account. For a tutorial on how to use this endpoint, see the [Registering and deregistering terminals](doc:registering-and-deregistering-terminals) topic in **Guides**. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments) and you must have an account with a gateway that supports terminal registration. ## Request parameters - terminalId ## Response parameters - terminalRegistrationStatus
- [Create simple login](https://docs.nexiopay.com/reference/createsimplelogin-1.md): Simple Login allows trusted users to proceed directly to the retail/MOTO iframe without entering a Nexio username and password. This option is useful for cases in which multiple users will be using a single Nexio account. It can also save time for internal users by eliminating the need to enter a username and password upon each use. Use the `key` value from the response as a query parameter in the request to load Nexio's retail iframe. For additional information about using this endpoint, see the [Using simple login for authentication](doc:using-simple-login-for-authentication) tutorial. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments) that you want to use for transactions and other tasks with the retail iframe. ## Response parameters - exp - jwt - key - refreshToken - username
- [View terminal list](https://docs.nexiopay.com/reference/viewterminallist-1.md): Retrieves a list of available terminals. You use the `terminalId` from this response in order to send a POST request to the [Process transaction from terminal](ref:processtransactionfromterminal) endpoint. > ๐ Note > > Terminals must be configured before they are available for processing. Depending on the terminal and your merchant account configuration, you need to either [pair the terminal](ref:pairterminal) or [register the terminal](ref:registerterminal). For additional information about this process, see the [Getting started with retail](doc:getting-started-with-retail) topic in Guides. > > If you do not see your terminal in the list retrieved through this endpoint, contact [Integrations Support](page:contact-us) for assistance. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Response parameters - gatewayLabel - gatewayName - gatewayType - merchantId - merchantName - terminalId - terminalName - terminalSerialNumber - terminalKey - terminalStatus
- [Process transaction from terminal](https://docs.nexiopay.com/reference/processtransactionfromterminal-1.md): Initiates a transaction through a terminal through the Nexio API rather than using the retail iframe. For more information on how to use this endpoint, see the steps in [Processing a transaction with a terminal](doc:processing-a-transaction-with-a-terminal) in Guides. You can also specify to save the card token from the terminal transaction so that you can use it for future transactions (through the [Run card transaction](ref:runcardtransaction) endpoint). > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). > > You must also have a terminal connected to the Nexio account. For more information, see the [Pair terminal](ref:pairterminal) or [Register terminal](ref:registerterminal) endpoints. ## Request parameters - data - data.amount - data.currency - data.customFields - data.customer - data.customer.customerRef - data.customer.orderNumber - data.customer.orderDate - data.customer.invoice - data.customer.firstName - data.customer.lastName - data.customer.birthDate - data.customer.nationalIdentificationNumber - data.customer.email - data.customer.phone - data.customer.billToAddressOne - data.customer.billToAddressTwo - data.customer.billToCity - data.customer.billToState - data.customer.billToPostal - data.customer.billToCountry - data.customer.billToPhone - data.customer.shipToAddressOne - data.customer.shipToAddressTwo - data.customer.shipToCity - data.customer.shipToState - data.customer.shipToPostal - data.customer.shipToCountry - data.customer.shipToPhone - data.description - data.lodging - data.lodging.advanceDeposit - data.lodging.checkInDate - data.lodging.checkOutDate - data.lodging.noShow - data.lodging.roomNumber - data.lodging.roomRate - terminalId - processingOptions.saveCardToken - isAuthOnly - card - card.cardHolderName ## Response parameters - terminalRequestId - terminalRequestStatus
- [View terminal transaction status](https://docs.nexiopay.com/reference/viewterminaltransactionstatus-1.md): Checks the status of a transaction run through a terminal. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - terminalRequestId ## Response parameters - gatewayResponse - gatewayResponse.gatewayName - currency - transactionStatus - terminal.token - terminalRequestId - authCode - transactionType - card - card.cardType - card.cardHolder - card.cardNumber - card.firstSix - card.lastFour - card.expirationMonth - card.expirationYear - processingOptions - processingOptions.merchantId - terminalRequestStatus - data - data.description - data.amount - data.currency - data.cart - data.cart.items - data.cart.items.item - data.cart.items.description - data.cart.items.quantity - data.cart.items.price - data.cart.items.type - data.customFields - data.customFields.exampleKey - data.customer - data.customer.firstName - data.customer.lastName - data.customer.customerRef - data.customer.orderNumber - data.customer.invoice - data.customer.email - data.customer.phone - data.customer.billToPhone - data.customer.billToAddressOne - data.customer.billToAddressTwo - data.customer.billToCity - data.customer.billToState - data.customer.billToPostal - data.customer.billToCountry - data.customer.shipToPhone - data.customer.shipToAddressOne - data.customer.shipToAddressTwo - data.customer.shipToCity - data.customer.shipToState - data.customer.shipToPostal - data.customer.shipToCountry - data.lodging - data.lodging.advanceDeposit - data.lodging.checkInDate - data.lodging.checkOutDate - data.lodging.noShow - data.lodging.roomNumber - data.lodging.roomRate - amount - transactionDate - id (this is the paymentId)
- [Pair terminal](https://docs.nexiopay.com/reference/pairterminal-1.md): Initiates pairing with a terminal. Depending on the merchant account configuration, when you add a terminal, you either need to request a pairing code or [add a registration code](ref:registerterminal). Some accounts may be configured to do both terminal setup options if the account is configured with multiple eligible gateways. For more information on how to pair a terminal, see [Pairing the terminal](doc:configuring-your-terminal-for-usaepay#pairing-the-terminal) in Guides. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - merchantId - terminalName ## Response parameters - terminalName - pairingCode - expirationDate - key
- [Register terminal](https://docs.nexiopay.com/reference/registerterminal-1.md): Provides a registration (or activation) code from a terminal to Nexio's API in order to register the terminal with the appropriate gateway. Depending on the merchant account configuration, when you add a terminal, you either need to add a registration code or [request a pairing code](ref:pairterminal). Some accounts may be configured to do both terminal setup options if the account is configured with multiple eligible gateways. If you are unsure which endpoint to use, please contact [Support](https://docs.nexiopay.com/page/contact-us). For a tutorial on how to use this endpoint, see the [Registering and deregistering terminals](doc:registering-and-deregistering-terminals) topic in **Guides**. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments) and you must have an account with a gateway that requires terminal registration. ## Request parameters - merchantId - terminalRegistrationCode - terminalName ## Response parameters - terminalName - deviceId - terminalSerialNumber - terminalRegistrationStatus - terminalId
- [Deregister terminal](https://docs.nexiopay.com/reference/deregisterterminal-1.md): Removes a terminal's registration through the Nexio API. > ๐ Notes > > - In addition to this API, you can deregister a terminal directly within the gateway user interface. > - You can only deregister terminals that have already been [registered](ref:registerterminal) with Nexio. > - You may need to deregister a terminal in situations such as when the terminal needs to be used with a different gateway account. For a tutorial on how to use this endpoint, see the [Registering and deregistering terminals](doc:registering-and-deregistering-terminals) topic in **Guides**. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments) and you must have an account with a gateway that supports terminal registration. ## Request parameters - terminalId ## Response parameters - terminalRegistrationStatus
- [Create a subscription](https://docs.nexiopay.com/reference/createsubscription.md): > ๐ Important > > Nexio does not currently recommend using the Subscription service for a 3DS flow. For other options, see [Getting started with subscriptions](doc:getting-started-with-subscriptions) in Guides. > Creates a recurring payment as a subscription or payment plan. For guides to using this endpoint, see the [Recurring billing overview](doc:recurring-billing-overview) topic. A successful request to this endpoint processes an initial transaction using a saved card token and schedules recurring transactions. All transactions are processed with the values provided in the `payment` object or the [data saved in the card token](doc:what-data-is-saved-with-tokens). The scheduled transaction runs according to the values provided in the `schedule` object. Also, in order to have a customer skip a month for an existing subscription or payment plan, you need to delete the current one and then recreate it to start with an `initialBillingAmount` of `0` and have the `dateInitialBillingEnd` happen a month before the next scheduled payment. > ๐ Note > > If the initial transaction is declined, the subscription or payment plan will not be created. It must be re-created with a new card token. > > After the subscription or payment plan is created, if a subsequent transaction gets declined or has an error, the system retries the transaction up to three times, one minute apart. On the third failure, the system stops trying for that installment, the subscription or payment plan remains active, and the system tries again at the next scheduled payment date. In this instance, the merchant would need to contact the customer about the missed payment or transaction. Also, if you have webhooks configured, you will receive a webhook for each of the failures. For additional information about this, see the [Creating a Nexio-scheduled card subscription](doc:creating-a-subscription) or [Creating a Nexio-scheduled card payment plan](doc:creating-a-pay-plan) tutorial. > > However, with [Decline recovery](doc:decline-recovery-overview) and when the subscription or payment plan was created with the `retryOnSoftDecline` parameter, instead of doing the three retries at a minute apart, the system retries according to the recommendation received from the Decline recovery system. > ๐ Important > > When needing to use a 3DS flow to create a subscription, you must first run a customer-facing transaction where the customer proceeds through the 3DS flow (see the [Using 3DS to run transactions](doc:using-3ds-to-run-transactions) tutorial). Make sure you use a `paymentType` of `initialScheduled` and also save the card token as part of the process. > > Then, use this endpoint to create the subscription with that saved card token and a `paymentType` of `scheduled`. > > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include at least a saved card token in the `tokenex.token` parameter, the amount and currency for the transaction, the payment type, and a customer reference number. You can also include the appropriate subscription parameters. ## Request parameters - payment - payment.tokenex - payment.tokenex.token - payment.tokenex.firstSix - payment.tokenex.lastFour - payment.isAuthOnly - payment.shouldUpdateCard - payment.processingOptions - payment.processingOptions.saveCardToken - payment.processingOptions.retryOnSoftDecline - payment.processingOptions.checkFraud - payment.processingOptions.shouldUseFingerprint - payment.processingOptions.check3ds - payment.processingOptions.verboseResponse - payment.processingOptions.paymentType - payment.processingOptions.paymentOptionTag - payment.processingOptions.merchantId - payment.processingOptions.customerRedirectUrl - payment.data - payment.data.amount - payment.data.currency - payment.data.settlementCurrency - payment.data.customer - payment.data.customer.customerRef - payment.data.customer.invoice - payment.data.customer.orderNumber - payment.data.customer.orderDate - payment.data.customer.birthDate - payment.data.customer.nationalIdentificationNumber - payment.data.customer.companyName - payment.data.customer.firstName - payment.data.customer.lastName - payment.data.customer.email - payment.data.customer.phone - payment.data.customer.billToAddressOne - payment.data.customer.billToAddressTwo - payment.data.customer.billToCity - payment.data.customer.billToState - payment.data.customer.billToPostal - payment.data.customer.billToCountry - payment.data.customer.billToPhone - payment.data.customer.shipToAddressOne - payment.data.customer.shipToAddressTwo - payment.data.customer.shipToCity - payment.data.customer.shipToState - payment.data.customer.shipToPostal - payment.data.customer.shipToCountry - payment.data.customer.shipToPhone - payment.data.customer.createdAtDate - schedule - schedule.interval - schedule.intervalCount - schedule.balance - schedule.duration - schedule.dateInitialBillingEnd - schedule.intialBillingAmount - schedule.dateCancelAfter ## Response parameters - customerRef - active - accountId - id - payment - payment.tokenex - payment.tokenex.token - payment.tokenex.firstSix - payment.tokenex.lastFour - payment.shouldUpdateCard - payment.isAuthOnly - payment.processingOptions - payment.processingOptions.saveCardToken - payment.processingOptions.retryOnSoftDecline - payment.processingOptions.checkFraud - payment.processingOptions.shouldUseFingerprint - payment.processingOptions.check3ds - payment.processingOptions.verboseResponse - payment.processingOptions.paymentType - payment.processingOptions.paymentOptionTag - payment.processingOptions.merchantId - payment.processingOptions.customerRedirectUrl - payment.data - payment.data.amount - payment.data.currency - payment.data.settlementCurrency - payment.data.customer - payment.data.customer.customerRef - payment.data.customer.invoice - payment.data.customer.orderNumber - payment.data.customer.orderDate - payment.data.customer.birthDate - payment.data.customer.nationalIdentificationNumber - payment.data.customer.companyName - payment.data.customer.firstName - payment.data.customer.lastName - payment.data.customer.email - payment.data.customer.phone - payment.data.customer.billToAddressOne - payment.data.customer.billToAddressTwo - payment.data.customer.billToCity - payment.data.customer.billToState - payment.data.customer.billToPostal - payment.data.customer.billToCountry - payment.data.customer.billToPhone - payment.data.customer.shipToAddressOne - payment.data.customer.shipToAddressTwo - payment.data.customer.shipToCity - payment.data.customer.shipToState - payment.data.customer.shipToPostal - payment.data.customer.shipToCountry - payment.data.customer.shipToPhone - payment.data.customer.createdAtDate - schedule - schedule.interval - schedule.intervalCount - schedule.initialBalance - schedule.balance - schedule.duration - schedule.dateInitialBillingEnd - schedule.intialBillingAmount - schedule.dateCancelAfter - schedule.scheduleType - userName - dateCreated - dateLastModified - dateLastRun - dateNextRun - paymentResult - paymentResult.amount - paymentResult.authCode - paymentResult.transactionStatus - paymentResult.transactionDate - paymentResult.transactionType - paymentResult.merchantId - paymentResult.currency - paymentResult.id - paymentResult.asyncTraceId - paymentResult.redirectUrl - paymentResult.message - paymentResult.status - paymentResult.gatewayResponse - paymentResult.gatewayResponse.gatewayName - paymentResult.gatewayResponse.refNumber - paymentResult.data - paymentResult.data.amount - paymentResult.data.currency - paymentResult.data.settlementCurrency - paymentResult.data.customer - paymentResult.data.customer.customerRef - paymentResult.data.customer.orderNumber - paymentResult.data.customer.orderDate - paymentResult.data.customer.invoice - paymentResult.data.customer.birthDate - paymentResult.data.customer.nationalIdentificationNumber - paymentResult.data.customer.companyName - paymentResult.data.customer.firstName - paymentResult.data.customer.lastName - paymentResult.data.customer.email - paymentResult.data.customer.phone - paymentResult.data.customer.billToAddressOne - paymentResult.data.customer.billToAddressTwo - paymentResult.data.customer.billToCity - paymentResult.data.customer.billToState - paymentResult.data.customer.billToPostal - paymentResult.data.customer.billToCountry - paymentResult.data.customer.billToPhone - paymentResult.data.customer.shipToAddressOne - paymentResult.data.customer.shipToAddressTwo - paymentResult.data.customer.shipToCity - paymentResult.data.customer.shipToState - paymentResult.data.customer.shipToPostal - paymentResult.data.customer.shipToCountry - paymentResult.data.customer.shipToPhone - paymentResult.data.customer.createdAt - paymentResult.card - paymentResult.card.cardHolder - paymentResult.card.cardNumber - paymentResult.card.expirationMonth - paymentResult.card.expirationYear - paymentResult.token - paymentResult.token.firstSix - paymentResult.token.lastFour - paymentResult.token.token - paymentResult.kountResponse - paymentResult.kountResponse.status - paymentResult.kountResponse.rules - lastPaymentStatus - lastSuccessfulPaymentDate - exp
- [View a subscription](https://docs.nexiopay.com/reference/viewsubscription.md): Returns the payment information and schedule for an existing subscription (or pay plan) based on the specified `id`. The ID needed for the path parameter is returned in the response for the [Create a subscription](ref:createsubscription) endpoint. Alternately, you can get the `id` for a subscription if you have a `customerRef` for the [View customer subscriptions](ref:viewcustomersubscriptions) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include a subscription ID in the path parameter of the request for a subscription created by the test account. ## Request parameters - id ## Response parameters - customerRef - active - accountId - id - payment - payment.tokenex - payment.tokenex.token - payment.tokenex.firstSix - payment.tokenex.lastFour - payment.shouldUpdateCard - payment.isAuthOnly - payment.processingOptions - payment.processingOptions.saveCardToken - payment.processingOptions.retryOnSoftDecline - payment.processingOptions.checkFraud - payment.processingOptions.shouldUseFingerprint - payment.processingOptions.check3ds - payment.processingOptions.verboseResponse - payment.processingOptions.paymentType - payment.processingOptions.paymentOptionTag - payment.processingOptions.merchantId - payment.processingOptions.customerRedirectUrl - payment.data - payment.data.amount - payment.data.currency - payment.data.settlementCurrency - payment.data.customer - payment.data.customer.customerRef - payment.data.customer.invoice - payment.data.customer.orderNumber - payment.data.customer.orderDate - payment.data.customer.birthDate - payment.data.customer.nationalIdentificationNumber - payment.data.customer.companyName - payment.data.customer.firstName - payment.data.customer.lastName - payment.data.customer.email - payment.data.customer.phone - payment.data.customer.billToAddressOne - payment.data.customer.billToAddressTwo - payment.data.customer.billToCity - payment.data.customer.billToState - payment.data.customer.billToPostal - payment.data.customer.billToCountry - payment.data.customer.billToPhone - payment.data.customer.shipToAddressOne - payment.data.customer.shipToAddressTwo - payment.data.customer.shipToCity - payment.data.customer.shipToState - payment.data.customer.shipToPostal - payment.data.customer.shipToCountry - payment.data.customer.shipToPhone - payment.data.customer.createdAtDate - schedule - schedule.interval - schedule.intervalCount - schedule.initialBalance - schedule.balance - schedule.duration - schedule.dateInitialBillingEnd - schedule.intialBillingAmount - schedule.dateCancelAfter - schedule.scheduleType - userName - dateCreated - dateLastModified - dateLastRun - dateNextRun - paymentResult - paymentResult.amount - paymentResult.authCode - paymentResult.transactionStatus - paymentResult.transactionDate - paymentResult.transactionType - paymentResult.merchantId - paymentResult.currency - paymentResult.id - paymentResult.asyncTraceId - paymentResult.redirectUrl - paymentResult.message - paymentResult.status - paymentResult.gatewayResponse - paymentResult.gatewayResponse.gatewayName - paymentResult.gatewayResponse.refNumber - paymentResult.data - paymentResult.data.amount - paymentResult.data.currency - paymentResult.data.settlementCurrency - paymentResult.data.customer - paymentResult.data.customer.customerRef - paymentResult.data.customer.orderNumber - paymentResult.data.customer.orderDate - paymentResult.data.customer.invoice - paymentResult.data.customer.birthDate - paymentResult.data.customer.nationalIdentificationNumber - paymentResult.data.customer.companyName - paymentResult.data.customer.firstName - paymentResult.data.customer.lastName - paymentResult.data.customer.email - paymentResult.data.customer.phone - paymentResult.data.customer.billToAddressOne - paymentResult.data.customer.billToAddressTwo - paymentResult.data.customer.billToCity - paymentResult.data.customer.billToState - paymentResult.data.customer.billToPostal - paymentResult.data.customer.billToCountry - paymentResult.data.customer.billToPhone - paymentResult.data.customer.shipToAddressOne - paymentResult.data.customer.shipToAddressTwo - paymentResult.data.customer.shipToCity - paymentResult.data.customer.shipToState - paymentResult.data.customer.shipToPostal - paymentResult.data.customer.shipToCountry - paymentResult.data.customer.shipToPhone - paymentResult.data.customer.createdAt - paymentResult.card - paymentResult.card.cardHolder - paymentResult.card.cardNumber - paymentResult.card.expirationMonth - paymentResult.card.expirationYear - paymentResult.token - paymentResult.token.firstSix - paymentResult.token.lastFour - paymentResult.token.token - paymentResult.kountResponse - paymentResult.kountResponse.status - paymentResult.kountResponse.rules - lastPaymentStatus - lastSuccessfulPaymentDate - exp
- [Update a subscription](https://docs.nexiopay.com/reference/updatesubscription.md): Updates an existing payment subscription or payment plan for the given `id`. The ID needed for the path parameter is returned in the response for the [Create a subscription](ref:createsubscription) endpoint. Alternately, you can get the `id` for a subscription if you have a `customerRef` for the [View customer subscriptions](ref:viewcustomersubscriptions) endpoint. > ๐ Note > > - Card token, currency, and customer reference number cannot be updated. If you need to change any of these values, [delete](ref:deletesubscription) the existing subscription or payment plan and [create](ref:createsubscription) a new one. > - For an existing payment plan, none of the schedule parameters can be updated. If you need to change any of those, [delete](ref:deletesubscription) the existing payment plan and [create](ref:createsubscription) a new one. > - The only user with rights to edit the subscription or payment plan is the original creator. See the `user` parameter that is returned in the [View a subscription](ref:viewsubscription) or [View customer subscriptions](ref:viewcustomersubscriptions) endpoints. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include a subscription ID in the path parameter of the request for a subscription created by the test account. ## Request parameters - id - payment - payment.tokenex - payment.tokenex.firstSix - payment.tokenex.lastFour - payment.isAuthOnly - payment.shouldUpdateCard - payment.processingOptions - payment.processingOptions.saveCardToken - payment.processingOptions.retryOnSoftDecline - payment.processingOptions.checkFraud - payment.processingOptions.shouldUseFingerprint - payment.processingOptions.check3ds - payment.processingOptions.verboseResponse - payment.processingOptions.paymentType - payment.processingOptions.paymentOptionTag - payment.processingOptions.merchantId - payment.processingOptions.customerRedirectUrl - payment.data - payment.data.settlementCurrency - payment.data.customer - payment.data.customer.invoice - payment.data.customer.orderNumber - payment.data.customer.orderDate - payment.data.customer.birthDate - payment.data.customer.nationalIdentificationNumber - payment.data.customer.companyName - payment.data.customer.firstName - payment.data.customer.lastName - payment.data.customer.email - payment.data.customer.phone - payment.data.customer.billToAddressOne - payment.data.customer.billToAddressTwo - payment.data.customer.billToCity - payment.data.customer.billToState - payment.data.customer.billToPostal - payment.data.customer.billToCountry - payment.data.customer.billToPhone - payment.data.customer.shipToAddressOne - payment.data.customer.shipToAddressTwo - payment.data.customer.shipToCity - payment.data.customer.shipToState - payment.data.customer.shipToPostal - payment.data.customer.shipToCountry - payment.data.customer.shipToPhone - payment.data.customer.createdAtDate - schedule - schedule.interval - schedule.intervalCount - schedule.duration - schedule.dateInitialBillingEnd - schedule.intialBillingAmount - schedule.dateCancelAfter ## Response parameters - customerRef - active - accountId - id - payment - payment.tokenex - payment.tokenex.token - payment.tokenex.firstSix - payment.tokenex.lastFour - payment.shouldUpdateCard - payment.isAuthOnly - payment.processingOptions - payment.processingOptions.saveCardToken - payment.processingOptions.retryOnSoftDecline - payment.processingOptions.checkFraud - payment.processingOptions.shouldUseFingerprint - payment.processingOptions.check3ds - payment.processingOptions.verboseResponse - payment.processingOptions.paymentType - payment.processingOptions.paymentOptionTag - payment.processingOptions.merchantId - payment.processingOptions.customerRedirectUrl - payment.data - payment.data.amount - payment.data.currency - payment.data.settlementCurrency - payment.data.customer - payment.data.customer.customerRef - payment.data.customer.invoice - payment.data.customer.orderNumber - payment.data.customer.orderDate - payment.data.customer.birthDate - payment.data.customer.nationalIdentificationNumber - payment.data.customer.companyName - payment.data.customer.firstName - payment.data.customer.lastName - payment.data.customer.email - payment.data.customer.phone - payment.data.customer.billToAddressOne - payment.data.customer.billToAddressTwo - payment.data.customer.billToCity - payment.data.customer.billToState - payment.data.customer.billToPostal - payment.data.customer.billToCountry - payment.data.customer.billToPhone - payment.data.customer.shipToAddressOne - payment.data.customer.shipToAddressTwo - payment.data.customer.shipToCity - payment.data.customer.shipToState - payment.data.customer.shipToPostal - payment.data.customer.shipToCountry - payment.data.customer.shipToPhone - payment.data.customer.createdAtDate - schedule - schedule.interval - schedule.intervalCount - schedule.initialBalance - schedule.balance - schedule.duration - schedule.dateInitialBillingEnd - schedule.intialBillingAmount - schedule.dateCancelAfter - schedule.scheduleType - userName - dateCreated - dateLastModified - dateLastRun - dateNextRun - paymentResult - paymentResult.amount - paymentResult.authCode - paymentResult.transactionStatus - paymentResult.transactionDate - paymentResult.transactionType - paymentResult.merchantId - paymentResult.currency - paymentResult.id - paymentResult.asyncTraceId - paymentResult.redirectUrl - paymentResult.message - paymentResult.status - paymentResult.gatewayResponse - paymentResult.gatewayResponse.gatewayName - paymentResult.gatewayResponse.refNumber - paymentResult.data - paymentResult.data.amount - paymentResult.data.currency - paymentResult.data.settlementCurrency - paymentResult.data.customer - paymentResult.data.customer.customerRef - paymentResult.data.customer.orderNumber - paymentResult.data.customer.orderDate - paymentResult.data.customer.invoice - paymentResult.data.customer.birthDate - paymentResult.data.customer.nationalIdentificationNumber - paymentResult.data.customer.companyName - paymentResult.data.customer.firstName - paymentResult.data.customer.lastName - paymentResult.data.customer.email - paymentResult.data.customer.phone - paymentResult.data.customer.billToAddressOne - paymentResult.data.customer.billToAddressTwo - paymentResult.data.customer.billToCity - paymentResult.data.customer.billToState - paymentResult.data.customer.billToPostal - paymentResult.data.customer.billToCountry - paymentResult.data.customer.billToPhone - paymentResult.data.customer.shipToAddressOne - paymentResult.data.customer.shipToAddressTwo - paymentResult.data.customer.shipToCity - paymentResult.data.customer.shipToState - paymentResult.data.customer.shipToPostal - paymentResult.data.customer.shipToCountry - paymentResult.data.customer.shipToPhone - paymentResult.data.customer.createdAt - paymentResult.card - paymentResult.card.cardHolder - paymentResult.card.cardNumber - paymentResult.card.expirationMonth - paymentResult.card.expirationYear - paymentResult.token - paymentResult.token.firstSix - paymentResult.token.lastFour - paymentResult.token.token - paymentResult.kountResponse - paymentResult.kountResponse.status - paymentResult.kountResponse.rules - lastPaymentStatus - lastSuccessfulPaymentDate - exp
- [Delete a subscription](https://docs.nexiopay.com/reference/deletesubscription.md): Deletes an existing payment subscription (or pay plan) based on the specified `id`. Deleting a subscription or payment plan cancels it so that the system does not run any more transactions for it. For a payment plan, this may mean that there is still an unpaid balance. The ID needed for the path parameter is returned in the response for the [Create a subscription](ref:createsubscription) endpoint. Alternately, you can get the `id` for a subscription if you have a `customerRef` for the [View customer subscriptions](ref:viewcustomersubscriptions) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include a subscription ID in the path parameter of the request for a subscription created by the test account. ## Request parameters - id ## Response parameters - message
- [View customer subscriptions](https://docs.nexiopay.com/reference/viewcustomersubscriptions.md): Returns a list of subscriptions and payment plans for a given customer reference number. This `customerRef` must have been used when creating the subscription or payment plan (see the [Create a subscription](ref:createsubscription) endpoint). > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include a customer reference number in the path parameter of the request for a subscription created by the test account. ## Request parameters - customerRef ## Response parameters - customerRef - active - accountId - id - payment - payment.tokenex - payment.tokenex.token - payment.tokenex.firstSix - payment.tokenex.lastFour - payment.shouldUpdateCard - payment.isAuthOnly - payment.processingOptions - payment.processingOptions.saveCardToken - payment.processingOptions.retryOnSoftDecline - payment.processingOptions.checkFraud - payment.processingOptions.shouldUseFingerprint - payment.processingOptions.check3ds - payment.processingOptions.verboseResponse - payment.processingOptions.paymentType - payment.processingOptions.paymentOptionTag - payment.processingOptions.merchantId - payment.processingOptions.customerRedirectUrl - payment.data - payment.data.amount - payment.data.currency - payment.data.settlementCurrency - payment.data.customer - payment.data.customer.customerRef - payment.data.customer.invoice - payment.data.customer.orderNumber - payment.data.customer.orderDate - payment.data.customer.birthDate - payment.data.customer.nationalIdentificationNumber - payment.data.customer.companyName - payment.data.customer.firstName - payment.data.customer.lastName - payment.data.customer.email - payment.data.customer.phone - payment.data.customer.billToAddressOne - payment.data.customer.billToAddressTwo - payment.data.customer.billToCity - payment.data.customer.billToState - payment.data.customer.billToPostal - payment.data.customer.billToCountry - payment.data.customer.billToPhone - payment.data.customer.shipToAddressOne - payment.data.customer.shipToAddressTwo - payment.data.customer.shipToCity - payment.data.customer.shipToState - payment.data.customer.shipToPostal - payment.data.customer.shipToCountry - payment.data.customer.shipToPhone - payment.data.customer.createdAtDate - schedule - schedule.interval - schedule.intervalCount - schedule.initialBalance - schedule.balance - schedule.duration - schedule.dateInitialBillingEnd - schedule.intialBillingAmount - schedule.dateCancelAfter - schedule.scheduleType - userName - dateCreated - dateLastModified - dateLastRun - dateNextRun - paymentResult - paymentResult.amount - paymentResult.authCode - paymentResult.transactionStatus - paymentResult.transactionDate - paymentResult.transactionType - paymentResult.merchantId - paymentResult.currency - paymentResult.id - paymentResult.asyncTraceId - paymentResult.redirectUrl - paymentResult.message - paymentResult.status - paymentResult.gatewayResponse - paymentResult.gatewayResponse.gatewayName - paymentResult.gatewayResponse.refNumber - paymentResult.data - paymentResult.data.amount - paymentResult.data.currency - paymentResult.data.settlementCurrency - paymentResult.data.customer - paymentResult.data.customer.customerRef - paymentResult.data.customer.orderNumber - paymentResult.data.customer.orderDate - paymentResult.data.customer.invoice - paymentResult.data.customer.birthDate - paymentResult.data.customer.nationalIdentificationNumber - paymentResult.data.customer.companyName - paymentResult.data.customer.firstName - paymentResult.data.customer.lastName - paymentResult.data.customer.email - paymentResult.data.customer.phone - paymentResult.data.customer.billToAddressOne - paymentResult.data.customer.billToAddressTwo - paymentResult.data.customer.billToCity - paymentResult.data.customer.billToState - paymentResult.data.customer.billToPostal - paymentResult.data.customer.billToCountry - paymentResult.data.customer.billToPhone - paymentResult.data.customer.shipToAddressOne - paymentResult.data.customer.shipToAddressTwo - paymentResult.data.customer.shipToCity - paymentResult.data.customer.shipToState - paymentResult.data.customer.shipToPostal - paymentResult.data.customer.shipToCountry - paymentResult.data.customer.shipToPhone - paymentResult.data.customer.createdAt - paymentResult.card - paymentResult.card.cardHolder - paymentResult.card.cardNumber - paymentResult.card.expirationMonth - paymentResult.card.expirationYear - paymentResult.token - paymentResult.token.firstSix - paymentResult.token.lastFour - paymentResult.token.token - paymentResult.kountResponse - paymentResult.kountResponse.status - paymentResult.kountResponse.rules - lastPaymentStatus - lastSuccessfulPaymentDate - exp
- [Create a subscription](https://docs.nexiopay.com/reference/createsubscription-1.md): > ๐ Important > > Nexio does not currently recommend using the Subscription service for a 3DS flow. For other options, see [Getting started with subscriptions](doc:getting-started-with-subscriptions) in Guides. > Creates a recurring payment as a subscription or payment plan. For guides to using this endpoint, see the [Recurring billing overview](doc:recurring-billing-overview) topic. A successful request to this endpoint processes an initial transaction using a saved card token and schedules recurring transactions. All transactions are processed with the values provided in the `payment` object or the [data saved in the card token](doc:what-data-is-saved-with-tokens). The scheduled transaction runs according to the values provided in the `schedule` object. Also, in order to have a customer skip a month for an existing subscription or payment plan, you need to delete the current one and then recreate it to start with an `initialBillingAmount` of `0` and have the `dateInitialBillingEnd` happen a month before the next scheduled payment. > ๐ Note > > If the initial transaction is declined, the subscription or payment plan will not be created. It must be re-created with a new card token. > > After the subscription or payment plan is created, if a subsequent transaction gets declined or has an error, the system retries the transaction up to three times, one minute apart. On the third failure, the system stops trying for that installment, the subscription or payment plan remains active, and the system tries again at the next scheduled payment date. In this instance, the merchant would need to contact the customer about the missed payment or transaction. Also, if you have webhooks configured, you will receive a webhook for each of the failures. For additional information about this, see the [Creating a Nexio-scheduled card subscription](doc:creating-a-subscription) or [Creating a Nexio-scheduled card payment plan](doc:creating-a-pay-plan) tutorial. > > However, with [Decline recovery](doc:decline-recovery-overview) and when the subscription or payment plan was created with the `retryOnSoftDecline` parameter, instead of doing the three retries at a minute apart, the system retries according to the recommendation received from the Decline recovery system. > ๐ Important > > When needing to use a 3DS flow to create a subscription, you must first run a customer-facing transaction where the customer proceeds through the 3DS flow (see the [Using 3DS to run transactions](doc:using-3ds-to-run-transactions) tutorial). Make sure you use a `paymentType` of `initialScheduled` and also save the card token as part of the process. > > Then, use this endpoint to create the subscription with that saved card token and a `paymentType` of `scheduled`. > > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include at least a saved card token in the `tokenex.token` parameter, the amount and currency for the transaction, the payment type, and a customer reference number. You can also include the appropriate subscription parameters. ## Request parameters - payment - payment.tokenex - payment.tokenex.token - payment.tokenex.firstSix - payment.tokenex.lastFour - payment.isAuthOnly - payment.shouldUpdateCard - payment.processingOptions - payment.processingOptions.saveCardToken - payment.processingOptions.retryOnSoftDecline - payment.processingOptions.checkFraud - payment.processingOptions.shouldUseFingerprint - payment.processingOptions.check3ds - payment.processingOptions.verboseResponse - payment.processingOptions.paymentType - payment.processingOptions.paymentOptionTag - payment.processingOptions.merchantId - payment.processingOptions.customerRedirectUrl - payment.data - payment.data.amount - payment.data.currency - payment.data.settlementCurrency - payment.data.customer - payment.data.customer.customerRef - payment.data.customer.invoice - payment.data.customer.orderNumber - payment.data.customer.orderDate - payment.data.customer.birthDate - payment.data.customer.nationalIdentificationNumber - payment.data.customer.companyName - payment.data.customer.firstName - payment.data.customer.lastName - payment.data.customer.email - payment.data.customer.phone - payment.data.customer.billToAddressOne - payment.data.customer.billToAddressTwo - payment.data.customer.billToCity - payment.data.customer.billToState - payment.data.customer.billToPostal - payment.data.customer.billToCountry - payment.data.customer.billToPhone - payment.data.customer.shipToAddressOne - payment.data.customer.shipToAddressTwo - payment.data.customer.shipToCity - payment.data.customer.shipToState - payment.data.customer.shipToPostal - payment.data.customer.shipToCountry - payment.data.customer.shipToPhone - payment.data.customer.createdAtDate - schedule - schedule.interval - schedule.intervalCount - schedule.balance - schedule.duration - schedule.dateInitialBillingEnd - schedule.intialBillingAmount - schedule.dateCancelAfter ## Response parameters - customerRef - active - accountId - id - payment - payment.tokenex - payment.tokenex.token - payment.tokenex.firstSix - payment.tokenex.lastFour - payment.shouldUpdateCard - payment.isAuthOnly - payment.processingOptions - payment.processingOptions.saveCardToken - payment.processingOptions.retryOnSoftDecline - payment.processingOptions.checkFraud - payment.processingOptions.shouldUseFingerprint - payment.processingOptions.check3ds - payment.processingOptions.verboseResponse - payment.processingOptions.paymentType - payment.processingOptions.paymentOptionTag - payment.processingOptions.merchantId - payment.processingOptions.customerRedirectUrl - payment.data - payment.data.amount - payment.data.currency - payment.data.settlementCurrency - payment.data.customer - payment.data.customer.customerRef - payment.data.customer.invoice - payment.data.customer.orderNumber - payment.data.customer.orderDate - payment.data.customer.birthDate - payment.data.customer.nationalIdentificationNumber - payment.data.customer.companyName - payment.data.customer.firstName - payment.data.customer.lastName - payment.data.customer.email - payment.data.customer.phone - payment.data.customer.billToAddressOne - payment.data.customer.billToAddressTwo - payment.data.customer.billToCity - payment.data.customer.billToState - payment.data.customer.billToPostal - payment.data.customer.billToCountry - payment.data.customer.billToPhone - payment.data.customer.shipToAddressOne - payment.data.customer.shipToAddressTwo - payment.data.customer.shipToCity - payment.data.customer.shipToState - payment.data.customer.shipToPostal - payment.data.customer.shipToCountry - payment.data.customer.shipToPhone - payment.data.customer.createdAtDate - schedule - schedule.interval - schedule.intervalCount - schedule.initialBalance - schedule.balance - schedule.duration - schedule.dateInitialBillingEnd - schedule.intialBillingAmount - schedule.dateCancelAfter - schedule.scheduleType - userName - dateCreated - dateLastModified - dateLastRun - dateNextRun - paymentResult - paymentResult.amount - paymentResult.authCode - paymentResult.transactionStatus - paymentResult.transactionDate - paymentResult.transactionType - paymentResult.merchantId - paymentResult.currency - paymentResult.id - paymentResult.asyncTraceId - paymentResult.redirectUrl - paymentResult.message - paymentResult.status - paymentResult.gatewayResponse - paymentResult.gatewayResponse.gatewayName - paymentResult.gatewayResponse.refNumber - paymentResult.data - paymentResult.data.amount - paymentResult.data.currency - paymentResult.data.settlementCurrency - paymentResult.data.customer - paymentResult.data.customer.customerRef - paymentResult.data.customer.orderNumber - paymentResult.data.customer.orderDate - paymentResult.data.customer.invoice - paymentResult.data.customer.birthDate - paymentResult.data.customer.nationalIdentificationNumber - paymentResult.data.customer.companyName - paymentResult.data.customer.firstName - paymentResult.data.customer.lastName - paymentResult.data.customer.email - paymentResult.data.customer.phone - paymentResult.data.customer.billToAddressOne - paymentResult.data.customer.billToAddressTwo - paymentResult.data.customer.billToCity - paymentResult.data.customer.billToState - paymentResult.data.customer.billToPostal - paymentResult.data.customer.billToCountry - paymentResult.data.customer.billToPhone - paymentResult.data.customer.shipToAddressOne - paymentResult.data.customer.shipToAddressTwo - paymentResult.data.customer.shipToCity - paymentResult.data.customer.shipToState - paymentResult.data.customer.shipToPostal - paymentResult.data.customer.shipToCountry - paymentResult.data.customer.shipToPhone - paymentResult.data.customer.createdAt - paymentResult.card - paymentResult.card.cardHolder - paymentResult.card.cardNumber - paymentResult.card.expirationMonth - paymentResult.card.expirationYear - paymentResult.token - paymentResult.token.firstSix - paymentResult.token.lastFour - paymentResult.token.token - paymentResult.kountResponse - paymentResult.kountResponse.status - paymentResult.kountResponse.rules - lastPaymentStatus - lastSuccessfulPaymentDate - exp
- [View subscriptions](https://docs.nexiopay.com/reference/viewsubscriptions.md): Returns the payment information and schedule for one or more existing subscriptions (or payment plans) based on the specified filter parameters. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
You do not have to include any query parameters, but you can include a value for how many results to return (`limit`), which Nexio account ID to limit results to (`accountId`), and whether to return only active subscriptions or payment plans (`active=true`). ## Request parameters - limit - accountId - active ## Response parameters - customerRef - active - accountId - id - payment - payment.tokenex - payment.tokenex.token - payment.tokenex.requestToken - payment.tokenex.firstSix - payment.tokenex.lastFour - payment.data - payment.data.amount - payment.data.currency - payment.data.customer - payment.data.customer.customerRef - payment.isPreExistingToken - payment.isProcessedFromServer - payment.subscriptionMetadata - payment.subscriptionMetadata.subscriptionId - payment.subscriptionMetadata.accountId - payment.subscriptionMetadata.isSubscriptionService - payment.clientIp - schedule - schedule.interval - schedule.intervalCount - schedule.initialBalance - schedule.balance - schedule.duration - schedule.dateInitialBillingEnd - schedule.intialBillingAmount - schedule.dateCancelAfter - schedule.scheduleType - userName - dateCreated - dateLastModified - dateLastRun - dateNextRun - paymentResult - paymentResult.gatewayProcessingError - paymentResult.message - paymentResult.gatewayResponse - paymentResult.gatewayResponse.gatewayName - paymentResult.gatewayResponse.refNumber - paymentResult.kountResults - paymentResult.kountResults.result - paymentResult.kountResults.message - paymentResult.merchantId - lastPaymentStatus - lastSuccessfulPaymentDate - exp
- [View a subscription](https://docs.nexiopay.com/reference/viewsubscription-1.md): Returns the payment information and schedule for an existing subscription (or pay plan) based on the specified `id`. The ID needed for the path parameter is returned in the response for the [Create a subscription](ref:createsubscription) endpoint. Alternately, you can get the `id` for a subscription if you have a `customerRef` for the [View customer subscriptions](ref:viewcustomersubscriptions) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include a subscription ID in the path parameter of the request for a subscription created by the test account. ## Request parameters - id ## Response parameters - customerRef - active - accountId - id - payment - payment.tokenex - payment.tokenex.token - payment.tokenex.firstSix - payment.tokenex.lastFour - payment.shouldUpdateCard - payment.isAuthOnly - payment.processingOptions - payment.processingOptions.saveCardToken - payment.processingOptions.retryOnSoftDecline - payment.processingOptions.checkFraud - payment.processingOptions.shouldUseFingerprint - payment.processingOptions.check3ds - payment.processingOptions.verboseResponse - payment.processingOptions.paymentType - payment.processingOptions.paymentOptionTag - payment.processingOptions.merchantId - payment.processingOptions.customerRedirectUrl - payment.data - payment.data.amount - payment.data.currency - payment.data.settlementCurrency - payment.data.customer - payment.data.customer.customerRef - payment.data.customer.invoice - payment.data.customer.orderNumber - payment.data.customer.orderDate - payment.data.customer.birthDate - payment.data.customer.nationalIdentificationNumber - payment.data.customer.companyName - payment.data.customer.firstName - payment.data.customer.lastName - payment.data.customer.email - payment.data.customer.phone - payment.data.customer.billToAddressOne - payment.data.customer.billToAddressTwo - payment.data.customer.billToCity - payment.data.customer.billToState - payment.data.customer.billToPostal - payment.data.customer.billToCountry - payment.data.customer.billToPhone - payment.data.customer.shipToAddressOne - payment.data.customer.shipToAddressTwo - payment.data.customer.shipToCity - payment.data.customer.shipToState - payment.data.customer.shipToPostal - payment.data.customer.shipToCountry - payment.data.customer.shipToPhone - payment.data.customer.createdAtDate - schedule - schedule.interval - schedule.intervalCount - schedule.initialBalance - schedule.balance - schedule.duration - schedule.dateInitialBillingEnd - schedule.intialBillingAmount - schedule.dateCancelAfter - schedule.scheduleType - userName - dateCreated - dateLastModified - dateLastRun - dateNextRun - paymentResult - paymentResult.amount - paymentResult.authCode - paymentResult.transactionStatus - paymentResult.transactionDate - paymentResult.transactionType - paymentResult.merchantId - paymentResult.currency - paymentResult.id - paymentResult.asyncTraceId - paymentResult.redirectUrl - paymentResult.message - paymentResult.status - paymentResult.gatewayResponse - paymentResult.gatewayResponse.gatewayName - paymentResult.gatewayResponse.refNumber - paymentResult.data - paymentResult.data.amount - paymentResult.data.currency - paymentResult.data.settlementCurrency - paymentResult.data.customer - paymentResult.data.customer.customerRef - paymentResult.data.customer.orderNumber - paymentResult.data.customer.orderDate - paymentResult.data.customer.invoice - paymentResult.data.customer.birthDate - paymentResult.data.customer.nationalIdentificationNumber - paymentResult.data.customer.companyName - paymentResult.data.customer.firstName - paymentResult.data.customer.lastName - paymentResult.data.customer.email - paymentResult.data.customer.phone - paymentResult.data.customer.billToAddressOne - paymentResult.data.customer.billToAddressTwo - paymentResult.data.customer.billToCity - paymentResult.data.customer.billToState - paymentResult.data.customer.billToPostal - paymentResult.data.customer.billToCountry - paymentResult.data.customer.billToPhone - paymentResult.data.customer.shipToAddressOne - paymentResult.data.customer.shipToAddressTwo - paymentResult.data.customer.shipToCity - paymentResult.data.customer.shipToState - paymentResult.data.customer.shipToPostal - paymentResult.data.customer.shipToCountry - paymentResult.data.customer.shipToPhone - paymentResult.data.customer.createdAt - paymentResult.card - paymentResult.card.cardHolder - paymentResult.card.cardNumber - paymentResult.card.expirationMonth - paymentResult.card.expirationYear - paymentResult.token - paymentResult.token.firstSix - paymentResult.token.lastFour - paymentResult.token.token - paymentResult.kountResponse - paymentResult.kountResponse.status - paymentResult.kountResponse.rules - lastPaymentStatus - lastSuccessfulPaymentDate - exp
- [Update a subscription](https://docs.nexiopay.com/reference/updatesubscription-1.md): Updates an existing payment subscription or payment plan for the given `id`. The ID needed for the path parameter is returned in the response for the [Create a subscription](ref:createsubscription) endpoint. Alternately, you can get the `id` for a subscription if you have a `customerRef` for the [View customer subscriptions](ref:viewcustomersubscriptions) endpoint. > ๐ Note > > - Card token, currency, and customer reference number cannot be updated. If you need to change any of these values, [delete](ref:deletesubscription) the existing subscription or payment plan and [create](ref:createsubscription) a new one. > - For an existing payment plan, none of the schedule parameters can be updated. If you need to change any of those, [delete](ref:deletesubscription) the existing payment plan and [create](ref:createsubscription) a new one. > - The only user with rights to edit the subscription or payment plan is the original creator. See the `user` parameter that is returned in the [View a subscription](ref:viewsubscription) or [View customer subscriptions](ref:viewcustomersubscriptions) endpoints. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include a subscription ID in the path parameter of the request for a subscription created by the test account. ## Request parameters - id - payment - payment.tokenex - payment.tokenex.firstSix - payment.tokenex.lastFour - payment.isAuthOnly - payment.shouldUpdateCard - payment.processingOptions - payment.processingOptions.saveCardToken - payment.processingOptions.retryOnSoftDecline - payment.processingOptions.checkFraud - payment.processingOptions.shouldUseFingerprint - payment.processingOptions.check3ds - payment.processingOptions.verboseResponse - payment.processingOptions.paymentType - payment.processingOptions.paymentOptionTag - payment.processingOptions.merchantId - payment.processingOptions.customerRedirectUrl - payment.data - payment.data.settlementCurrency - payment.data.customer - payment.data.customer.invoice - payment.data.customer.orderNumber - payment.data.customer.orderDate - payment.data.customer.birthDate - payment.data.customer.nationalIdentificationNumber - payment.data.customer.companyName - payment.data.customer.firstName - payment.data.customer.lastName - payment.data.customer.email - payment.data.customer.phone - payment.data.customer.billToAddressOne - payment.data.customer.billToAddressTwo - payment.data.customer.billToCity - payment.data.customer.billToState - payment.data.customer.billToPostal - payment.data.customer.billToCountry - payment.data.customer.billToPhone - payment.data.customer.shipToAddressOne - payment.data.customer.shipToAddressTwo - payment.data.customer.shipToCity - payment.data.customer.shipToState - payment.data.customer.shipToPostal - payment.data.customer.shipToCountry - payment.data.customer.shipToPhone - payment.data.customer.createdAtDate - schedule - schedule.interval - schedule.intervalCount - schedule.duration - schedule.dateInitialBillingEnd - schedule.intialBillingAmount - schedule.dateCancelAfter ## Response parameters - customerRef - active - accountId - id - payment - payment.tokenex - payment.tokenex.token - payment.tokenex.firstSix - payment.tokenex.lastFour - payment.shouldUpdateCard - payment.isAuthOnly - payment.processingOptions - payment.processingOptions.saveCardToken - payment.processingOptions.retryOnSoftDecline - payment.processingOptions.checkFraud - payment.processingOptions.shouldUseFingerprint - payment.processingOptions.check3ds - payment.processingOptions.verboseResponse - payment.processingOptions.paymentType - payment.processingOptions.paymentOptionTag - payment.processingOptions.merchantId - payment.processingOptions.customerRedirectUrl - payment.data - payment.data.amount - payment.data.currency - payment.data.settlementCurrency - payment.data.customer - payment.data.customer.customerRef - payment.data.customer.invoice - payment.data.customer.orderNumber - payment.data.customer.orderDate - payment.data.customer.birthDate - payment.data.customer.nationalIdentificationNumber - payment.data.customer.companyName - payment.data.customer.firstName - payment.data.customer.lastName - payment.data.customer.email - payment.data.customer.phone - payment.data.customer.billToAddressOne - payment.data.customer.billToAddressTwo - payment.data.customer.billToCity - payment.data.customer.billToState - payment.data.customer.billToPostal - payment.data.customer.billToCountry - payment.data.customer.billToPhone - payment.data.customer.shipToAddressOne - payment.data.customer.shipToAddressTwo - payment.data.customer.shipToCity - payment.data.customer.shipToState - payment.data.customer.shipToPostal - payment.data.customer.shipToCountry - payment.data.customer.shipToPhone - payment.data.customer.createdAtDate - schedule - schedule.interval - schedule.intervalCount - schedule.initialBalance - schedule.balance - schedule.duration - schedule.dateInitialBillingEnd - schedule.intialBillingAmount - schedule.dateCancelAfter - schedule.scheduleType - userName - dateCreated - dateLastModified - dateLastRun - dateNextRun - paymentResult - paymentResult.amount - paymentResult.authCode - paymentResult.transactionStatus - paymentResult.transactionDate - paymentResult.transactionType - paymentResult.merchantId - paymentResult.currency - paymentResult.id - paymentResult.asyncTraceId - paymentResult.redirectUrl - paymentResult.message - paymentResult.status - paymentResult.gatewayResponse - paymentResult.gatewayResponse.gatewayName - paymentResult.gatewayResponse.refNumber - paymentResult.data - paymentResult.data.amount - paymentResult.data.currency - paymentResult.data.settlementCurrency - paymentResult.data.customer - paymentResult.data.customer.customerRef - paymentResult.data.customer.orderNumber - paymentResult.data.customer.orderDate - paymentResult.data.customer.invoice - paymentResult.data.customer.birthDate - paymentResult.data.customer.nationalIdentificationNumber - paymentResult.data.customer.companyName - paymentResult.data.customer.firstName - paymentResult.data.customer.lastName - paymentResult.data.customer.email - paymentResult.data.customer.phone - paymentResult.data.customer.billToAddressOne - paymentResult.data.customer.billToAddressTwo - paymentResult.data.customer.billToCity - paymentResult.data.customer.billToState - paymentResult.data.customer.billToPostal - paymentResult.data.customer.billToCountry - paymentResult.data.customer.billToPhone - paymentResult.data.customer.shipToAddressOne - paymentResult.data.customer.shipToAddressTwo - paymentResult.data.customer.shipToCity - paymentResult.data.customer.shipToState - paymentResult.data.customer.shipToPostal - paymentResult.data.customer.shipToCountry - paymentResult.data.customer.shipToPhone - paymentResult.data.customer.createdAt - paymentResult.card - paymentResult.card.cardHolder - paymentResult.card.cardNumber - paymentResult.card.expirationMonth - paymentResult.card.expirationYear - paymentResult.token - paymentResult.token.firstSix - paymentResult.token.lastFour - paymentResult.token.token - paymentResult.kountResponse - paymentResult.kountResponse.status - paymentResult.kountResponse.rules - lastPaymentStatus - lastSuccessfulPaymentDate - exp
- [Delete a subscription](https://docs.nexiopay.com/reference/deletesubscription-1.md): Deletes an existing payment subscription (or pay plan) based on the specified `id`. Deleting a subscription or payment plan cancels it so that the system does not run any more transactions for it. For a payment plan, this may mean that there is still an unpaid balance. The ID needed for the path parameter is returned in the response for the [Create a subscription](ref:createsubscription) endpoint. Alternately, you can get the `id` for a subscription if you have a `customerRef` for the [View customer subscriptions](ref:viewcustomersubscriptions) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include a subscription ID in the path parameter of the request for a subscription created by the test account. ## Request parameters - id ## Response parameters - message
- [View customer subscriptions](https://docs.nexiopay.com/reference/viewcustomersubscriptions-1.md): Returns a list of subscriptions and payment plans for a given customer reference number. This `customerRef` must have been used when creating the subscription or payment plan (see the [Create a subscription](ref:createsubscription) endpoint). > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include a customer reference number in the path parameter of the request for a subscription created by the test account. ## Request parameters - customerRef ## Response parameters - customerRef - active - accountId - id - payment - payment.tokenex - payment.tokenex.token - payment.tokenex.firstSix - payment.tokenex.lastFour - payment.shouldUpdateCard - payment.isAuthOnly - payment.processingOptions - payment.processingOptions.saveCardToken - payment.processingOptions.retryOnSoftDecline - payment.processingOptions.checkFraud - payment.processingOptions.shouldUseFingerprint - payment.processingOptions.check3ds - payment.processingOptions.verboseResponse - payment.processingOptions.paymentType - payment.processingOptions.paymentOptionTag - payment.processingOptions.merchantId - payment.processingOptions.customerRedirectUrl - payment.data - payment.data.amount - payment.data.currency - payment.data.settlementCurrency - payment.data.customer - payment.data.customer.customerRef - payment.data.customer.invoice - payment.data.customer.orderNumber - payment.data.customer.orderDate - payment.data.customer.birthDate - payment.data.customer.nationalIdentificationNumber - payment.data.customer.companyName - payment.data.customer.firstName - payment.data.customer.lastName - payment.data.customer.email - payment.data.customer.phone - payment.data.customer.billToAddressOne - payment.data.customer.billToAddressTwo - payment.data.customer.billToCity - payment.data.customer.billToState - payment.data.customer.billToPostal - payment.data.customer.billToCountry - payment.data.customer.billToPhone - payment.data.customer.shipToAddressOne - payment.data.customer.shipToAddressTwo - payment.data.customer.shipToCity - payment.data.customer.shipToState - payment.data.customer.shipToPostal - payment.data.customer.shipToCountry - payment.data.customer.shipToPhone - payment.data.customer.createdAtDate - schedule - schedule.interval - schedule.intervalCount - schedule.initialBalance - schedule.balance - schedule.duration - schedule.dateInitialBillingEnd - schedule.intialBillingAmount - schedule.dateCancelAfter - schedule.scheduleType - userName - dateCreated - dateLastModified - dateLastRun - dateNextRun - paymentResult - paymentResult.amount - paymentResult.authCode - paymentResult.transactionStatus - paymentResult.transactionDate - paymentResult.transactionType - paymentResult.merchantId - paymentResult.currency - paymentResult.id - paymentResult.asyncTraceId - paymentResult.redirectUrl - paymentResult.message - paymentResult.status - paymentResult.gatewayResponse - paymentResult.gatewayResponse.gatewayName - paymentResult.gatewayResponse.refNumber - paymentResult.data - paymentResult.data.amount - paymentResult.data.currency - paymentResult.data.settlementCurrency - paymentResult.data.customer - paymentResult.data.customer.customerRef - paymentResult.data.customer.orderNumber - paymentResult.data.customer.orderDate - paymentResult.data.customer.invoice - paymentResult.data.customer.birthDate - paymentResult.data.customer.nationalIdentificationNumber - paymentResult.data.customer.companyName - paymentResult.data.customer.firstName - paymentResult.data.customer.lastName - paymentResult.data.customer.email - paymentResult.data.customer.phone - paymentResult.data.customer.billToAddressOne - paymentResult.data.customer.billToAddressTwo - paymentResult.data.customer.billToCity - paymentResult.data.customer.billToState - paymentResult.data.customer.billToPostal - paymentResult.data.customer.billToCountry - paymentResult.data.customer.billToPhone - paymentResult.data.customer.shipToAddressOne - paymentResult.data.customer.shipToAddressTwo - paymentResult.data.customer.shipToCity - paymentResult.data.customer.shipToState - paymentResult.data.customer.shipToPostal - paymentResult.data.customer.shipToCountry - paymentResult.data.customer.shipToPhone - paymentResult.data.customer.createdAt - paymentResult.card - paymentResult.card.cardHolder - paymentResult.card.cardNumber - paymentResult.card.expirationMonth - paymentResult.card.expirationYear - paymentResult.token - paymentResult.token.firstSix - paymentResult.token.lastFour - paymentResult.token.token - paymentResult.kountResponse - paymentResult.kountResponse.status - paymentResult.kountResponse.rules - lastPaymentStatus - lastSuccessfulPaymentDate - exp
- [Create APM one-time-use token](https://docs.nexiopay.com/reference/createapmonetimeusetoken.md): A token from this endpoint is necessary prior to loading any of the Alternative Payment Method (APM) iframes or running a transaction using an APM. Any data (amount, currency, and so forth) that you want to be sent to the alternate payment method must be included in the body of this request. For details about each APM, as well as test cards and accounts, see [Payment methods](doc:payment-methods). For a tutorial about how to make use of this endpoint, see the [Run a sale transaction](doc:run-a-sale-transaction) topic. > ๐ Note > > After a token has been used to submit an iframe it cannot be used to load another. You must request a new APM one-time-use token prior to submitting each iframe. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account (that is connected with [PayPal](doc:paypal-integration-guide)). Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include any other parameters that you need for the body of the request, depending on what you are using the one-time-use token for, and which payment method you want to use. For details about each one, as well as test cards and accounts, see [Payment methods](doc:payment-methods). ## Request parameters - isAuthOnly - data - data.amount - data.currency - data.customer - data.customer.email - data.customer.firstName - data.customer.lastName - data.customer.customerRef - data.customer.orderNumber - data.customer.billToAddressOne - data.customer.billToAddressTwo - data.customer.billToCity - data.customer.billToCountry - data.customer.billToPhone - data.customer.billToPostal - data.customer.billToState - data.customer.birthDate - data.customer.invoice - data.customer.shipToAddressOne - data.customer.shipToAddressTwo - data.customer.shipToCity - data.customer.shipToCountry - data.customer.shipToPhone - data.customer.shipToPostal - data.customer.shipToState - data.cart - data.cart.items - data.cart.items.item - data.cart.items.description - data.cart.items.quantity - data.cart.items.price - data.cart.items.type - data.cart.items.imageUrl - data.cart.items.productUrl - data.customFields - data.customFields.exampleKey - data.description - data.descriptor - data.descriptor.name - data.descriptor.address - data.descriptor.city - data.descriptor.state - data.descriptor.postal - data.descriptor.country - data.descriptor.phone - data.descriptor.url - data.descriptor.merchantId - data.descriptor.mcc - data.dueDate - data.locale - data.paymentMethod - customerRedirectUrl - processingOptions - processingOptions.merchantId - processingOptions.doNotProcessPayment - processingOptions.paymentOptionTag - processingOptions.saveRecurringToken - uiOptions - uiOptions.displaySubmitButton - uiOptions.css ## Response parameters - expiration - token - asyncTraceId - expressIFrameUrl - redirectUrls - redirectUrls.paymentMethod - redirectUrls.url - buttonIFrameUrls - buttonIFrameUrls.paymentMethod - buttonIFrameUrls.url
- [Get APM iframe](https://docs.nexiopay.com/reference/getapmiframe.md): Returns HTML for an iframe that allows a user to redirect to the chosen alternative payment method's web page in a new window. The alternative payment method must be chosen upon retrieval of an [APM one-time-use token](ref:createapmonetimeusetoken). > ๐ Note > > Only use this endpoint when you are not using one of the standard integration methods. For more information about those standard methods, see the [Supported integration methods for APMs](doc:supported-integration-methods-for-apms) topic. > > This iframe emits events, alerting you when the transaction has been submitted, processed, and so forth. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must first request an [APM one-time-use token](ref:createapmonetimeusetoken). ## Request parameters - token ## Response parameters - HTML page
- [Run APM transaction](https://docs.nexiopay.com/reference/runapmtransaction.md): Allows you to securely process an alternative payment method transaction without a browser, such as for merchant-initiated transactions using [PayPal (with Braintree)](doc:paypal-with-braintree-integration-guide). > ๐ Note > > In order to use this endpoint, the following two things must be true: > - You must have already set `processingOptions.saveRecurringToken` to `true` in the [APM one-time-use token](ref:createapmonetimeusetoken) request for the initial transaction. > - Your customer must have already checked out and paid through the alternative payment method for that initial transaction. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - apm - apm.token - data - data.amount - data.currency - data.customer - data.customer.orderNumber - data.customer.billToAddressOne - data.customer.billToAddressTwo - data.customer.billToCity - data.customer.billToCountry - data.customer.billToPhone - data.customer.billToPostal - data.customer.billToState - data.customer.birthDate - data.customer.companyName - data.customer.createdAtDate - data.customer.customerRef - data.customer.email - data.customer.invoice - data.customer.firstName - data.customer.lastName - data.customer.orderDate - data.customer.phone - data.customer.shipToAddressOne - data.customer.shipToAddressTwo - data.customer.shipToCity - data.customer.shipToCountry - data.customer.shipToPhone - data.customer.shipToPostal - data.customer.shipToState - data.customFields - data.customFields.exampleKey - data.description - isAuthOnly - processingOptions - processingOptions.merchantId - processingOptions.paymentOptionTag - processingOptions.webhookFailUrl ## Response parameters - id - merchantId - transactionDate - transactionStatus - amount - transactionType - currency - gatewayResponse - gatewayResponse.gatewayName - gatewayResponse.refNumber - data - data.amount - data.currency - data.settlementCurrency - data.customer - data.customer.customerRef - data.customer.orderNumber - data.customer.orderDate - data.customer.invoice - data.customer.firstName - data.customer.lastName - data.customer.birthDate - data.customer.billToAddressOne - data.customer.billToAddressTwo - data.customer.billToCity - data.customer.billToCountry - data.customer.billToPhone - data.customer.billToPostal - data.customer.billToState - data.customer.email - data.customer.phone - data.customer.shipToAddressOne - data.customer.shipToAddressTwo - data.customer.shipToCity - data.customer.shipToCountry - data.customer.shipToPhone - data.customer.shipToPostal - data.customer.shipToState - data.customer.createdAt - data.customFields - data.customFields.exampleKey - data.description - apm - apm.token
- [View APM transaction async status](https://docs.nexiopay.com/reference/viewapmtransactionasyncstatus.md): Gets information about the specified alternative payment method (APM) asynchronous transaction. Use this for tracking APM transactions submitted through the [Run APM transaction](ref:runapmtransaction) or through any of the integration methods (for more information, see [Run a sale transaction](doc:run-a-sale-transaction) in the Alternative Payment Method section of Guides). The [Create APM one-time-use token](ref:createapmonetimeusetoken) endpoint returns the `asyncTraceId` in the response for you to use with the path parameter for this endpoint. For the [Multi Iframe (Express APM)](doc:multi-iframe-express-apm) and [Individual Iframe (Button URLs)](doc:individual-iframe-button-urls) integration methods for one-time payments (non-dropin-style), the history object progresses through the following flow for a successful payment:- `getToken`
- `iframe`
- `popup`
- `finale`
For the [Custom Redirect (Redirect URLs)](doc:custom-redirect-redirect-urls) integration method, the history object progresses through the following flow for a successful payment:- `getToken`
- `popup`
- `finale`
For first transactions in a [merchant-initiated recurring transaction](doc:run-a-merchant-initiated-recurring-transaction), the history object progressess through the following flow for a successful payment:- `getToken`
- `iframe`
- `processFromApm`
### See also - For tracking 3DS transactions, see the [View transaction async status](ref:viewtransactionasyncstatus) endpoint. ## Request parameters - asyncTraceId ## Response parameters - gatewayResponse - gatewayResponse.refNumber - gatewayResponse.gatewayName - history.processFromApm - history.processFromApm.initiatedAt - history.processFromApm.updatedAt - history.processFromApm.state - history.getToken - history.getToken.initiatedAt - history.getToken.updatedAt - history.getToken.state - history.iframe - history.iframe.initiatedAt - history.iframe.updatedAt - history.iframe.state - history.popup - history.popup.initiatedAt - history.popup.updatedAt - history.popup.state - history.finale - history.finale.initiatedAt - history.finale.updatedAt - history.finale.state - updatedAt - initialTransactionStatus - createdAt - asyncTraceId
- [Capture an APM transaction](https://docs.nexiopay.com/reference/captureapmtransaction.md): Captures a previously authorized (auth only) transaction run using an Alternative Payment Method (see the [Create APM one-time-use token ](ref:createapmonetimeusetoken) endpoint). If you do not know the `paymentId` or `amount` to use, make a call with the [View transactions](ref:viewtransactions) endpoint with the query filter of `transactionStatus=11` and `plugin=` to get an array of possible transactions. For more help with this endpoint, see the [Capture an auth-only APM transaction](doc:capture-an-auth-only-apm-transaction) tutorial in Guides. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account (that is connected with [PayPal](doc:paypal-integration-guide)). Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include the ID of the payment request and the amount of the transaction in your request. ## Request parameters - id - data - data.amount ## Response parameters - id - merchantId - transactionDate - amount - transactionType - currency - gatewayResponse - gatewayResponse.gatewayName - gatewayResponse.refNumber - data - data.amount - data.currency - data.settlementCurrency - message
- [Void an APM transaction](https://docs.nexiopay.com/reference/voidapmtransaction.md): Voids a transaction run using an Alternative Payment Method. If you do not know the `paymentId` or `amount` to use, make a call with the [View transactions](ref:viewtransactions) endpoint with the query filter of `transactionStatus=10` and `plugin=` to get an array of possible transactions that have authorized but are not yet settled. For more help with this endpoint, see the [Void an APM transaction](doc:void-an-apm-transaction) tutorial in Guides. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account (that is connected with [PayPal](doc:paypal-integration-guide)). Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include the paymentID of the transaction in your request. ## Request parameters - id - data - data.amount ## Response parameters - id - merchantId - transactionDate - amount - transactionType - currency - gatewayResponse - gatewayResponse.gatewayName - gatewayResponse.refNumber - data - data.amount - data.currency - data.settlementCurrency - message
- [Refund an APM transaction](https://docs.nexiopay.com/reference/refundapmtransaction.md): Refunds a transaction using an Alternative Payment Method. If you do not know the `paymentId` or `amount` to use, make a call with the [View transactions](ref:viewtransactions) endpoint with the query filter of `transactionStatus=10` and `plugin=` to get an array of possible transactions that have authorized or `transactionStatus=20` and `plugin=` for transactions that are settled. For more help with this endpoint, see the [Refund a transaction](doc:refund-a-transaction) tutorial in Guides. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account (that is connected with [PayPal](doc:paypal-integration-guide)). Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include the ID of the payment request and the amount of the transaction in your request. ## Request parameters - id - data - data.amount ## Response parameters - id - merchantId - transactionDate - amount - transactionType - currency - gatewayResponse - gatewayResponse.gatewayName - gatewayResponse.refNumber - data - data.amount - data.currency - data.settlementCurrency - message
- [Create APM one-time-use token](https://docs.nexiopay.com/reference/createapmonetimeusetoken-1.md): A token from this endpoint is necessary prior to loading any of the Alternative Payment Method (APM) iframes or running a transaction using an APM. Any data (amount, currency, and so forth) that you want to be sent to the alternate payment method must be included in the body of this request. For details about each APM, as well as test cards and accounts, see [Payment methods](doc:payment-methods). For a tutorial about how to make use of this endpoint, see the [Run a sale transaction](doc:run-a-sale-transaction) topic. > ๐ Note > > After a token has been used to submit an iframe it cannot be used to load another. You must request a new APM one-time-use token prior to submitting each iframe. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account (that is connected with [PayPal](doc:paypal-integration-guide)). Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include any other parameters that you need for the body of the request, depending on what you are using the one-time-use token for, and which payment method you want to use. For details about each one, as well as test cards and accounts, see [Payment methods](doc:payment-methods). ## Request parameters - isAuthOnly - data - data.amount - data.currency - data.customer - data.customer.email - data.customer.firstName - data.customer.lastName - data.customer.customerRef - data.customer.orderNumber - data.customer.billToAddressOne - data.customer.billToAddressTwo - data.customer.billToCity - data.customer.billToCountry - data.customer.billToPhone - data.customer.billToPostal - data.customer.billToState - data.customer.birthDate - data.customer.invoice - data.customer.shipToAddressOne - data.customer.shipToAddressTwo - data.customer.shipToCity - data.customer.shipToCountry - data.customer.shipToPhone - data.customer.shipToPostal - data.customer.shipToState - data.cart - data.cart.items - data.cart.items.item - data.cart.items.description - data.cart.items.quantity - data.cart.items.price - data.cart.items.type - data.cart.items.imageUrl - data.cart.items.productUrl - data.customFields - data.customFields.exampleKey - data.description - data.descriptor - data.descriptor.name - data.descriptor.address - data.descriptor.city - data.descriptor.state - data.descriptor.postal - data.descriptor.country - data.descriptor.phone - data.descriptor.url - data.descriptor.merchantId - data.descriptor.mcc - data.dueDate - data.locale - data.paymentMethod - customerRedirectUrl - processingOptions - processingOptions.merchantId - processingOptions.doNotProcessPayment - processingOptions.paymentOptionTag - processingOptions.saveRecurringToken - uiOptions - uiOptions.displaySubmitButton - uiOptions.css ## Response parameters - expiration - token - asyncTraceId - expressIFrameUrl - redirectUrls - redirectUrls.paymentMethod - redirectUrls.url - buttonIFrameUrls - buttonIFrameUrls.paymentMethod - buttonIFrameUrls.url
- [Get APM iframe](https://docs.nexiopay.com/reference/getapmiframe-1.md): Returns HTML for an iframe that allows a user to redirect to the chosen alternative payment method's web page in a new window. The alternative payment method must be chosen upon retrieval of an [APM one-time-use token](ref:createapmonetimeusetoken). > ๐ Note > > Only use this endpoint when you are not using one of the standard integration methods. For more information about those standard methods, see the [Supported integration methods for APMs](doc:supported-integration-methods-for-apms) topic. > > This iframe emits events, alerting you when the transaction has been submitted, processed, and so forth. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must first request an [APM one-time-use token](ref:createapmonetimeusetoken). ## Request parameters - token ## Response parameters - HTML page
- [Run APM transaction](https://docs.nexiopay.com/reference/runapmtransaction-1.md): Allows you to securely process an alternative payment method transaction without a browser, such as for merchant-initiated transactions using [PayPal (with Braintree)](doc:paypal-with-braintree-integration-guide). > ๐ Note > > In order to use this endpoint, the following two things must be true: > - You must have already set `processingOptions.saveRecurringToken` to `true` in the [APM one-time-use token](ref:createapmonetimeusetoken) request for the initial transaction. > - Your customer must have already checked out and paid through the alternative payment method for that initial transaction. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - apm - apm.token - data - data.amount - data.currency - data.customer - data.customer.orderNumber - data.customer.billToAddressOne - data.customer.billToAddressTwo - data.customer.billToCity - data.customer.billToCountry - data.customer.billToPhone - data.customer.billToPostal - data.customer.billToState - data.customer.birthDate - data.customer.companyName - data.customer.createdAtDate - data.customer.customerRef - data.customer.email - data.customer.invoice - data.customer.firstName - data.customer.lastName - data.customer.orderDate - data.customer.phone - data.customer.shipToAddressOne - data.customer.shipToAddressTwo - data.customer.shipToCity - data.customer.shipToCountry - data.customer.shipToPhone - data.customer.shipToPostal - data.customer.shipToState - data.customFields - data.customFields.exampleKey - data.description - isAuthOnly - processingOptions - processingOptions.merchantId - processingOptions.paymentOptionTag - processingOptions.webhookFailUrl ## Response parameters - id - merchantId - transactionDate - transactionStatus - amount - transactionType - currency - gatewayResponse - gatewayResponse.gatewayName - gatewayResponse.refNumber - data - data.amount - data.currency - data.settlementCurrency - data.customer - data.customer.customerRef - data.customer.orderNumber - data.customer.orderDate - data.customer.invoice - data.customer.firstName - data.customer.lastName - data.customer.birthDate - data.customer.billToAddressOne - data.customer.billToAddressTwo - data.customer.billToCity - data.customer.billToCountry - data.customer.billToPhone - data.customer.billToPostal - data.customer.billToState - data.customer.email - data.customer.phone - data.customer.shipToAddressOne - data.customer.shipToAddressTwo - data.customer.shipToCity - data.customer.shipToCountry - data.customer.shipToPhone - data.customer.shipToPostal - data.customer.shipToState - data.customer.createdAt - data.customFields - data.customFields.exampleKey - data.description - apm - apm.token
- [View APM transaction async status](https://docs.nexiopay.com/reference/viewapmtransactionasyncstatus-1.md): Gets information about the specified alternative payment method (APM) asynchronous transaction. Use this for tracking APM transactions submitted through the [Run APM transaction](ref:runapmtransaction) or through any of the integration methods (for more information, see [Run a sale transaction](doc:run-a-sale-transaction) in the Alternative Payment Method section of Guides). The [Create APM one-time-use token](ref:createapmonetimeusetoken) endpoint returns the `asyncTraceId` in the response for you to use with the path parameter for this endpoint. For the [Multi Iframe (Express APM)](doc:multi-iframe-express-apm) and [Individual Iframe (Button URLs)](doc:individual-iframe-button-urls) integration methods for one-time payments (non-dropin-style), the history object progresses through the following flow for a successful payment:- `getToken`
- `iframe`
- `popup`
- `finale`
For the [Custom Redirect (Redirect URLs)](doc:custom-redirect-redirect-urls) integration method, the history object progresses through the following flow for a successful payment:- `getToken`
- `popup`
- `finale`
For first transactions in a [merchant-initiated recurring transaction](doc:run-a-merchant-initiated-recurring-transaction), the history object progressess through the following flow for a successful payment:- `getToken`
- `iframe`
- `processFromApm`
### See also - For tracking 3DS transactions, see the [View transaction async status](ref:viewtransactionasyncstatus) endpoint. ## Request parameters - asyncTraceId ## Response parameters - gatewayResponse - gatewayResponse.refNumber - gatewayResponse.gatewayName - history.processFromApm - history.processFromApm.initiatedAt - history.processFromApm.updatedAt - history.processFromApm.state - history.getToken - history.getToken.initiatedAt - history.getToken.updatedAt - history.getToken.state - history.iframe - history.iframe.initiatedAt - history.iframe.updatedAt - history.iframe.state - history.popup - history.popup.initiatedAt - history.popup.updatedAt - history.popup.state - history.finale - history.finale.initiatedAt - history.finale.updatedAt - history.finale.state - updatedAt - initialTransactionStatus - createdAt - asyncTraceId
- [Capture an APM transaction](https://docs.nexiopay.com/reference/captureapmtransaction-1.md): Captures a previously authorized (auth only) transaction run using an Alternative Payment Method (see the [Create APM one-time-use token ](ref:createapmonetimeusetoken) endpoint). If you do not know the `paymentId` or `amount` to use, make a call with the [View transactions](ref:viewtransactions) endpoint with the query filter of `transactionStatus=11` and `plugin=` to get an array of possible transactions. For more help with this endpoint, see the [Capture an auth-only APM transaction](doc:capture-an-auth-only-apm-transaction) tutorial in Guides. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account (that is connected with [PayPal](doc:paypal-integration-guide)). Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include the ID of the payment request and the amount of the transaction in your request. ## Request parameters - id - data - data.amount ## Response parameters - id - merchantId - transactionDate - amount - transactionType - currency - gatewayResponse - gatewayResponse.gatewayName - gatewayResponse.refNumber - data - data.amount - data.currency - data.settlementCurrency - message
- [Void an APM transaction](https://docs.nexiopay.com/reference/voidapmtransaction-1.md): Voids a transaction run using an Alternative Payment Method. If you do not know the `paymentId` or `amount` to use, make a call with the [View transactions](ref:viewtransactions) endpoint with the query filter of `transactionStatus=10` and `plugin=` to get an array of possible transactions that have authorized but are not yet settled. For more help with this endpoint, see the [Void an APM transaction](doc:void-an-apm-transaction) tutorial in Guides. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account (that is connected with [PayPal](doc:paypal-integration-guide)). Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include the paymentID of the transaction in your request. ## Request parameters - id - data - data.amount ## Response parameters - id - merchantId - transactionDate - amount - transactionType - currency - gatewayResponse - gatewayResponse.gatewayName - gatewayResponse.refNumber - data - data.amount - data.currency - data.settlementCurrency - message
- [Refund an APM transaction](https://docs.nexiopay.com/reference/refundapmtransaction-1.md): Refunds a transaction using an Alternative Payment Method. If you do not know the `paymentId` or `amount` to use, make a call with the [View transactions](ref:viewtransactions) endpoint with the query filter of `transactionStatus=10` and `plugin=` to get an array of possible transactions that have authorized or `transactionStatus=20` and `plugin=` for transactions that are settled. For more help with this endpoint, see the [Refund a transaction](doc:refund-a-transaction) tutorial in Guides. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account (that is connected with [PayPal](doc:paypal-integration-guide)). Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include the ID of the payment request and the amount of the transaction in your request. ## Request parameters - id - data - data.amount ## Response parameters - id - merchantId - transactionDate - amount - transactionType - currency - gatewayResponse - gatewayResponse.gatewayName - gatewayResponse.refNumber - data - data.amount - data.currency - data.settlementCurrency - message
- [Create a recipient](https://docs.nexiopay.com/reference/createrecipient.md): Creates a recipient profile to which payments can be sent. A recipient is the individual or business receiving payments. Before paying out to a recipient, you must first create a recipient profile, either as a separate process or at the same time as the [payout request](ref:submitpayouts). > ๐ Note > > For the payout provider Interchecks, if you pass a value for one of the `recipientIdNumbers` parameters when creating a new recipient, you cannot update any recipient information with [Update recipient](ref:updaterecipient) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include at least a `recipientRef`, recipient `email`, recipient `firstName` and `lastName`, and the `country` for the recipient. ## Request parameters - recipientRef - email - firstName - lastName - country - providerId - userType - gender - birthDate - countryOfBirth - countryOfNationality - currency - addressType - addressLine1 - addressLine2 - city - region - postalCode - phoneNumber - phoneNumberCountry - mobileNumber - mobileNumberCountry - governmentIdType - recipientIdNumbers - recipientIdNumbers.governmentId - recipientIdNumbers.passportId - recipientIdNumbers.employerId - recipientIdNumbers.driversLicenseId ## Response parameters - recipientRef - recipientId - payoutAccountId - providerId - providerType - providerRecipientRef - userType - firstName - lastName - gender - birthDate - countryOfBirth - countryOfNationality - addressLine1 - addressLine2 - city - region - postalCode - country - email - phoneNumber - mobileNumber - governmentIdType - recipientIdNumbers - recipientIdNumbers.governmentId - recipientIdNumbers.passportId - recipientIdNumbers.employerId - recipientIdNumbers.driversLicenseId - createdAt - updatedAt
- [View recipients](https://docs.nexiopay.com/reference/viewrecipients.md): Returns all recipients that meet the specified parameters (if any) and that are associated with the Nexio account used to [authenticate](doc:authentication). You may also request to return additional parameters and/or filter results using one or more [query parameters](doc:filtering-using-query-parameters). > ๐ Notes > > For example, to return (filter) all recipients where the address' country is NL and also (request to include) the `recipientIdNumbers` object in the response, the request would look like this: > /payout/v3/recipient?recipientIdNumbers.&country=NL
To return (filter) only the recipient with the specified `recipientRef` parameter, the request would look like this: > /payout/v3/recipient?recipientRef=10524260
For a more detailed tutorial, see the [query parameters](doc:filtering-using-query-parameters) section of Guides. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - limit - offset - startDate - endDate - recipientId - recipientRef - providerRecipientRef - providerType - email - firstName - lastName - phoneNumber - mobileNumber - addressLine1 - addressLine2 - city - region - postalCode - country - countryOfBirth - countryOfNationality - providerId - payoutAccountId - recipientIdNumbers - recipientIdNumbers.governmentId - recipientIdNumbers.passportId - recipientIdNumbers.employerId - recipientIdNumbers.driversLicenseId - userType - birthDate - gender - addressType - phoneNumberCountry - mobileNumberCountry - governmentIdType - createdAt - updatedAt ## Response parameters - offset - limit - rows - rows.recipientRef - rows.recipientId - rows.payoutAccountId - rows.providerId - rows.providerType - rows.providerRecipientRef - rows.userType - rows.firstName - rows.lastName - rows.gender - rows.birthDate - rows.countryOfBirth - rows.countryOfNationality - rows.addressLine1 - rows.addressLine2 - rows.city - rows.region - rows.postalCode - rows.country - rows.email - rows.phoneNumber - rows.mobileNumber - rows.governmentIdType - rows.recipientIdNumbers - rows.recipientIdNumbers.governmentId - rows.recipientIdNumbers.passportId - rows.recipientIdNumbers.employerId - rows.recipientIdNumbers.driversLicenseId - rows.createdAt - rows.updatedAt - hasMore
- [Update recipient](https://docs.nexiopay.com/reference/updaterecipient.md): This endpoint is used to update information for an existing payout recipient. > ๐ Important > > You can only update a recipient record if the request is accepted by the payout provider associated with the `recipientId`. > ๐ Note > > For the payout provider Interchecks, if you pass a value for one of the `recipientIdNumbers` parameters when creating a new recipient, you cannot update any recipient information with this endpoint.
In the case that a value has been passed for the `recipientIdNumbers` and you are wanting to change information for an existing Interchecks recipient, contact Interchecks to update the recipient's information. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include at least a `recipienId` and recipient `firstName` and `lastName`. ## Request parameters - recipientId - firstName - lastName - recipientIdNumbers - recipientIdNumbers.governmentId - recipientIdNumbers.passportId - recipientIdNumbers.employerId - recipientIdNumbers.driversLicenseId - providerId - recipientRef - email - userType - gender - birthDate - countryOfBirth - countryOfNationality - country - currency - addressType - addressLine1 - addressLine2 - city - region - postalCode - phoneNumber - phoneNumberCountry - mobileNumber - mobileNumberCountry ## Response parameters - payoutAccountId - providerId - recipientId - recipientRef - email - firstName - lastName - providerType - providerRecipientRef - userType - addressLine1 - addressLine2 - city - region - postalCode - country - phoneNumber - mobileNumber - countryOfBirth - countryOfNationality - gender - birthDate - recipientRulesMetadata - recipientRulesMetadata.id - recipientRulesMetadata.recipientId - recipientRulesMetadata.metadata - recipientRulesMetadata.createdAt - recipientRulesMetadata.updatedAt - recipientIdNumbers - recipientIdNumbers.governmentId - recipientIdNumbers.passportId - recipientIdNumbers.employerId - recipientIdNumbers.driversLicenseId - createdAt - updatedAt
- [View a recipient by recipientId](https://docs.nexiopay.com/reference/viewrecipientbyrecipientid.md): Searches for recipients with the specified `recipientId`. > ๐ Notes > > - You can only use `recipientId` as the path parameter for this endpoint. > - When searching for a recipient by `recipientRef` use the [View a recipient by recipientRef](ref:viewrecipientbyrecipientref) endpoint. > - To view a recipient using other IDs or parameters, use the [View recipients](ref:viewrecipients) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include the `recipientId` in the path parameter of the request. ## Request parameters - recipientId ## Response parameters - recipientRef - recipientId - payoutAccountId - providerId - providerType - providerRecipientRef - userType - firstName - lastName - gender - birthDate - countryOfBirth - countryOfNationality - addressLine1 - addressLine2 - city - region - postalCode - country - email - phoneNumber - mobileNumber - governmentIdType - recipientIdNumbers - recipientIdNumbers.governmentId - recipientIdNumbers.passportId - recipientIdNumbers.employerId - recipientIdNumbers.driversLicenseId - createdAt - updatedAt
- [View a recipient by recipientRef](https://docs.nexiopay.com/reference/viewrecipientbyrecipientref.md): Searches for recipients with the specified `recipientRef`. > ๐ Notes > > - You can only use `recipientRef` as the path parameter for this endpoint. > - When searching for a recipient by `recipientId` use the [View a recipient by recipientId](ref:viewrecipientbyrecipientid) endpoint. > - To view a recipient using other IDs or parameters, use the [View recipients](ref:viewrecipients) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include the `recipientRef` in the path parameter of the request. ## Request parameters - recipientRef ## Response parameters - recipientRef - recipientId - payoutAccountId - providerId - providerType - providerRecipientRef - userType - firstName - lastName - gender - birthDate - countryOfBirth - countryOfNationality - addressLine1 - addressLine2 - city - region - postalCode - country - email - phoneNumber - mobileNumber - governmentIdType - recipientIdNumbers - recipientIdNumbers.governmentId - recipientIdNumbers.passportId - recipientIdNumbers.employerId - recipientIdNumbers.driversLicenseId - createdAt - updatedAt
- [Create a recipient](https://docs.nexiopay.com/reference/createrecipient-1.md): Creates a recipient profile to which payments can be sent. A recipient is the individual or business receiving payments. Before paying out to a recipient, you must first create a recipient profile, either as a separate process or at the same time as the [payout request](ref:submitpayouts). > ๐ Note > > For the payout provider Interchecks, if you pass a value for one of the `recipientIdNumbers` parameters when creating a new recipient, you cannot update any recipient information with [Update recipient](ref:updaterecipient) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include at least a `recipientRef`, recipient `email`, recipient `firstName` and `lastName`, and the `country` for the recipient. ## Request parameters - recipientRef - email - firstName - lastName - country - providerId - userType - gender - birthDate - countryOfBirth - countryOfNationality - currency - addressType - addressLine1 - addressLine2 - city - region - postalCode - phoneNumber - phoneNumberCountry - mobileNumber - mobileNumberCountry - governmentIdType - recipientIdNumbers - recipientIdNumbers.governmentId - recipientIdNumbers.passportId - recipientIdNumbers.employerId - recipientIdNumbers.driversLicenseId ## Response parameters - recipientRef - recipientId - payoutAccountId - providerId - providerType - providerRecipientRef - userType - firstName - lastName - gender - birthDate - countryOfBirth - countryOfNationality - addressLine1 - addressLine2 - city - region - postalCode - country - email - phoneNumber - mobileNumber - governmentIdType - recipientIdNumbers - recipientIdNumbers.governmentId - recipientIdNumbers.passportId - recipientIdNumbers.employerId - recipientIdNumbers.driversLicenseId - createdAt - updatedAt
- [View recipients](https://docs.nexiopay.com/reference/viewrecipients-1.md): Returns all recipients that meet the specified parameters (if any) and that are associated with the Nexio account used to [authenticate](doc:authentication). You may also request to return additional parameters and/or filter results using one or more [query parameters](doc:filtering-using-query-parameters). > ๐ Notes > > For example, to return (filter) all recipients where the address' country is NL and also (request to include) the `recipientIdNumbers` object in the response, the request would look like this: > /payout/v3/recipient?recipientIdNumbers.&country=NL
To return (filter) only the recipient with the specified `recipientRef` parameter, the request would look like this: > /payout/v3/recipient?recipientRef=10524260
For a more detailed tutorial, see the [query parameters](doc:filtering-using-query-parameters) section of Guides. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - limit - offset - startDate - endDate - recipientId - recipientRef - providerRecipientRef - providerType - email - firstName - lastName - phoneNumber - mobileNumber - addressLine1 - addressLine2 - city - region - postalCode - country - countryOfBirth - countryOfNationality - providerId - payoutAccountId - recipientIdNumbers - recipientIdNumbers.governmentId - recipientIdNumbers.passportId - recipientIdNumbers.employerId - recipientIdNumbers.driversLicenseId - userType - birthDate - gender - addressType - phoneNumberCountry - mobileNumberCountry - governmentIdType - createdAt - updatedAt ## Response parameters - offset - limit - rows - rows.recipientRef - rows.recipientId - rows.payoutAccountId - rows.providerId - rows.providerType - rows.providerRecipientRef - rows.userType - rows.firstName - rows.lastName - rows.gender - rows.birthDate - rows.countryOfBirth - rows.countryOfNationality - rows.addressLine1 - rows.addressLine2 - rows.city - rows.region - rows.postalCode - rows.country - rows.email - rows.phoneNumber - rows.mobileNumber - rows.governmentIdType - rows.recipientIdNumbers - rows.recipientIdNumbers.governmentId - rows.recipientIdNumbers.passportId - rows.recipientIdNumbers.employerId - rows.recipientIdNumbers.driversLicenseId - rows.createdAt - rows.updatedAt - hasMore
- [Update recipient](https://docs.nexiopay.com/reference/updaterecipient-1.md): This endpoint is used to update information for an existing payout recipient. > ๐ Important > > You can only update a recipient record if the request is accepted by the payout provider associated with the `recipientId`. > ๐ Note > > For the payout provider Interchecks, if you pass a value for one of the `recipientIdNumbers` parameters when creating a new recipient, you cannot update any recipient information with this endpoint.
In the case that a value has been passed for the `recipientIdNumbers` and you are wanting to change information for an existing Interchecks recipient, contact Interchecks to update the recipient's information. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include at least a `recipienId` and recipient `firstName` and `lastName`. ## Request parameters - recipientId - firstName - lastName - recipientIdNumbers - recipientIdNumbers.governmentId - recipientIdNumbers.passportId - recipientIdNumbers.employerId - recipientIdNumbers.driversLicenseId - providerId - recipientRef - email - userType - gender - birthDate - countryOfBirth - countryOfNationality - country - currency - addressType - addressLine1 - addressLine2 - city - region - postalCode - phoneNumber - phoneNumberCountry - mobileNumber - mobileNumberCountry ## Response parameters - payoutAccountId - providerId - recipientId - recipientRef - email - firstName - lastName - providerType - providerRecipientRef - userType - addressLine1 - addressLine2 - city - region - postalCode - country - phoneNumber - mobileNumber - countryOfBirth - countryOfNationality - gender - birthDate - recipientRulesMetadata - recipientRulesMetadata.id - recipientRulesMetadata.recipientId - recipientRulesMetadata.metadata - recipientRulesMetadata.createdAt - recipientRulesMetadata.updatedAt - recipientIdNumbers - recipientIdNumbers.governmentId - recipientIdNumbers.passportId - recipientIdNumbers.employerId - recipientIdNumbers.driversLicenseId - createdAt - updatedAt
- [View a recipient by recipientId](https://docs.nexiopay.com/reference/viewrecipientbyrecipientid-1.md): Searches for recipients with the specified `recipientId`. > ๐ Notes > > - You can only use `recipientId` as the path parameter for this endpoint. > - When searching for a recipient by `recipientRef` use the [View a recipient by recipientRef](ref:viewrecipientbyrecipientref) endpoint. > - To view a recipient using other IDs or parameters, use the [View recipients](ref:viewrecipients) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include the `recipientId` in the path parameter of the request. ## Request parameters - recipientId ## Response parameters - recipientRef - recipientId - payoutAccountId - providerId - providerType - providerRecipientRef - userType - firstName - lastName - gender - birthDate - countryOfBirth - countryOfNationality - addressLine1 - addressLine2 - city - region - postalCode - country - email - phoneNumber - mobileNumber - governmentIdType - recipientIdNumbers - recipientIdNumbers.governmentId - recipientIdNumbers.passportId - recipientIdNumbers.employerId - recipientIdNumbers.driversLicenseId - createdAt - updatedAt
- [View a recipient by recipientRef](https://docs.nexiopay.com/reference/viewrecipientbyrecipientref-1.md): Searches for recipients with the specified `recipientRef`. > ๐ Notes > > - You can only use `recipientRef` as the path parameter for this endpoint. > - When searching for a recipient by `recipientId` use the [View a recipient by recipientId](ref:viewrecipientbyrecipientid) endpoint. > - To view a recipient using other IDs or parameters, use the [View recipients](ref:viewrecipients) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include the `recipientRef` in the path parameter of the request. ## Request parameters - recipientRef ## Response parameters - recipientRef - recipientId - payoutAccountId - providerId - providerType - providerRecipientRef - userType - firstName - lastName - gender - birthDate - countryOfBirth - countryOfNationality - addressLine1 - addressLine2 - city - region - postalCode - country - email - phoneNumber - mobileNumber - governmentIdType - recipientIdNumbers - recipientIdNumbers.governmentId - recipientIdNumbers.passportId - recipientIdNumbers.employerId - recipientIdNumbers.driversLicenseId - createdAt - updatedAt
- [Submit payouts](https://docs.nexiopay.com/reference/submitpayouts.md): Allows you to submit one or more payouts in the body of an API request. Payouts can be made to existing recipients or you can create a recipient at the same time as submitting a payout by including the amount and currency for the payout as well as the required parameters for a recipient. ### Required payout parameters The required parameters for a payout are the following:
- `amount`
- `currency`
- The **required recipient parameters** ### Required recipient parameters For sending a payout to an **existing recipient**, you must specify one or more of the following recipient parameters (if you specify more than one, they are prioritized in the given order):
- `recipientRef`
- `recipientId`
- `email`
**Note:** The system ignores any other recipient parameters that you include.
For sending a payout to a **new recipient**, you must include at least the following recipient parameters:
- `recipientRef`
- `email`
- `firstName`
- `lastName`
- `country`
You may also optionally include any of the other parameters for [creating a recipient](ref:createrecipient). > ๐ Note > > For the payout provider Interchecks, if you pass a value for one of the `recipientIdNumbers` parameters when creating a new recipient, you cannot update any recipient information with [Update recipient](ref:updaterecipient) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include all the required parameters for a payout and a recipient, depending on whether this is for a new or existing recipient (see above). ## Request parameters - payouts - payouts.amount - payouts.currency - payouts.recipient - payouts.recipient.recipientRef - payouts.recipient.recipientId - payouts.recipient.email - payouts.recipient.firstName - payouts.recipient.lastName - payouts.recipient.country - payouts.recipient.providerId - payouts.recipient.userType - payouts.recipient.gender - payouts.recipient.birthDate - payouts.recipient.countryOfBirth - payouts.recipient.countryOfNationality - payouts.recipient.currency - payouts.recipient.addressType - payouts.recipient.addressLine1 - payouts.recipient.addressLine2 - payouts.recipient.city - payouts.recipient.region - payouts.recipient.postalCode - payouts.recipient.phoneNumber - payouts.recipient.phoneNumberCountry - payouts.recipient.mobileNumber - payouts.recipient.mobileNumberCountry - payouts.recipient.governmentIdType - payouts.recipient.recipientIdNumbers - payouts.recipient.recipientIdNumbers.governmentId - payouts.recipient.recipientIdNumbers.passportId - payouts.recipient.recipientIdNumbers.employerId - payouts.recipient.recipientIdNumbers.driversLicenseId - payouts.description - payouts.payoutRef - batchRef ## Response parameters - message
- [Submit payouts using batch file](https://docs.nexiopay.com/reference/payoutbatch.md): Allows you to submit one or more payouts using a batch file as input for the API request. Use this endpoint to make payouts to existing or new recipients. > ๐ Important > > Ensure the following for this endpoint:- The header content-type must be `multipart/form-data`.
- The batch file must be in a location that is accessible by the server making this API request.
> ๐ Note > > For the payout provider Interchecks, if you pass a value for one of the `recipientIdNumbers` parameters when creating a new recipient, you cannot update any recipient information with [Update recipient](ref:updaterecipient) endpoint. > โ ๏ธ Try It > > Due to technical limitations, it is not possible to use the Try It feature with this endpoint. Instead, use Postman or your own server (along with the credentials for your [Sandbox API user](doc:sandbox-environments)) to make the request. ## Batch file parameters The following table shows the required and optional parameters for making payouts using a batch file. For more information about each parameter, see the [Submit payouts](ref:submitpayouts) endpoint. To use your own field headers from your batch file, contact [Integrations Support](page:contact-us) for assistance. | Parameter | Name in batch file | Notes |
| batchRef | batchRef | If you include this parameter, the system only uses the first instance of it in the batch file. Other instances are ignored. If you want multiple batches to display as a single group in a report, specify the same value for each batch. Using this option allows you to easily view money sent to different payout providers so that you can properly fund those accounts. |
| currency | currency | Required for each payout. |
| amount | amount | Required for each payout. |
| description | description | Optional. |
| payoutRef | payoutRef | Optional. |
| recipient.recipientId | recipientId | Conditionally required for payout to an existing recipient when neither `recipientRef` nor `email` is included. This parameter is prioritized if more than one of those is included.
Not allowed for payout to a new recipient. |
| recipient.recipientRef | recipientRef | Conditionally required for payout to an existing recipient when neither `recipientId` nor `email` is included. This parameter is prioritized over email if that value is included. Otherwise, it is ignored if `recipientId` is included.
Required for payout to a new recipient.
Important: We strongly recommend that you include this value in your request instead of recipientId in order to facilitate payment reconciliation. |
| recipient.email | email | Conditionally required for payout to an existing recipient when neither `recipientId` nor `recipientRef` is included. This parameter is only prioritized if neither of the other two are included. Otherwise, it is ignored.
Required for payout to a new recipient. |
| recipient.firstName | firstName | Required for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.lastName | lastName | Required for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.country | country | Required for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.providerId | providerId | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.userType | userType | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.gender | gender | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.birthDate | birthDate | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.countryOfBirth | countryOfBirth | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.countryOfNationality | countryOfNationality | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.addressType | addressType | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.addressLine1 | addressLine1 | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.addressLine2 | addressLine2 | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.city | city | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.region | region | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.postalCode | postalCode | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.phoneNumber | phoneNumber | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.phoneNumberCountry | phoneNumberCountry | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.mobileNumber | mobileNumber | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.mobileNumberCountry | mobileNumberCountry | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.governmentIdType | governmentIdType | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
governmentId (in recipient.recipientIdNumbers) | governmentId | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
passportId (in recipient.recipientIdNumbers) | passportId | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
driversLicenseId (in recipient.recipientIdNumbers) | driversLicenseId | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
employerId (in recipient.recipientIdNumbers) | employerId | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
## Batch file format and examples The batch file needs to be in CSV format. The first line contains a comma-separated list of the parameters to use. Each subsequent line must have the same number of commas as the first line but does not have to have content for each parameter (except where the parameter is required for the payout request). For the possible required, conditionally required, and optional parameters to include, see the previous section. To use your own field headers from your batch file, contact [Integrations Support](page:contact-us) for assistance. ### Simple batch file example ``` firstName,lastName,recipientRef,email,country,amount,currency Yiseme,Gordman,9348rwf2,ygordman@testdata123.com,US,15,USD John,Johnson,123456r3,jj@123.com,CA,140,CAD ,,,,,, ``` [Download sample file (in ZIP)](https://drive.google.com/file/d/1rR_knD7aBeCUnTvbHATOrPsW5lsuz-BI/view?usp=sharing)
(To download, click the link and then select the option to "download".) ### Batch file with all parameters example ``` batchRef,currency,amount,description,payoutRef,recipientId,recipientRef,email,firstName,lastName,country,providerId,userType,gender,birthDate,countryOfBirth,countryOfNationality,addressType,addressLine1,addressLine2,city,region,postalCode,phoneNumber,phoneNumberCountry,mobileNumber,mobileNumberCountry,governmentIdType,governmentId,passportId,driversLicenseId,employerId batch006,USD,1314.27,June commission payment,113e9ee19a-9c5f-49ca-9a92-3e39e64219c01,98198452,DS1125345,recipientemail112@payoutnow.com,Judith,Callie,US,12695,INDIVIDUAL,FEMALE,12/5/90,US,US,RESIDENTIAL,123 Somewhere St,,Somewhere,AK,99885,801111111,US,8012222222,US,NATIONALIDCARD,999999999,,DL12343234, batch006,USD,125,June commission payment,Z12345 June 15th compensation pay1,98468985,Z11223456,recipientemai1l21@payoutnow.com,Merchnat,LLC,ES,12686,BUSINESS,MALE,11/19/91,ES,ES,BUSINESS,"C. del Pozo, 8",,Madrid,,28012,34915223894,ES,34915223895,ES,NATIONALIDCARD,,,,111111111 batch006,CAD,161.13,June commission payment,11a5ff4a13d4381,,RR12234346,recipientemail132@payoutnow.com,Wilimina,Manning,CA,12696,INDIVIDUAL,FEMALE,1/15/93,CA,CA,RESIDENTIAL,800 Benevenuto Ave,,Brentwood Bay,BC,V8M 1J8,2506524422,CA,2506524421,CA,PASSPORT,,789546512,, ``` [Download sample batch file (in ZIP)](https://drive.google.com/file/d/1JYmaQCyfQRy6ioMn5mZPVvFTGk2xgySC/view?usp=sharing)
(To download, click the link and then select the option to "download".)
- [View a payout](https://docs.nexiopay.com/reference/viewpayout.md): Searches for payouts with the given `payoutId`. > ๐ Note > > The `payoutId` parameter is not the same as the `payoutRef`, `payoutProviderRef`, or `payoutProviderAdditionalRef`. To view a payout using one of these other reference values, use the [View payouts](ref:viewpayouts) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include the payout ID in the path parameter of the request. ## Request parameters - payoutId ## Response parameters - batchRef - id - recipientRef - recipientId - payoutAccountId - payoutRef - providerId - providerType - payoutProviderRef - payoutProviderAdditionalRef - providerRecipientRef - amount - currency - description - payoutDate - transferStatus - payoutStatus - providerResponse - firstName - lastName - addressLine1 - addressLine2 - city - region - postalCode - country - email - phoneNumber - mobileNumber - createdAt - updatedAt
- [View payouts](https://docs.nexiopay.com/reference/viewpayouts.md): Returns all payouts that meet the specified parameters (if any) and that are associated with the Nexio account used to [authenticate](doc:authentication). This is the only endpoint where you can use `payoutRef` in the request to view a specific payout based on that value. You may also request to return additional parameters and/or filter results using one or more [query parameters](doc:filtering-using-query-parameters). > ๐ Notes > > By way of example, to return (filter) all payouts where the currency is EUR and also (request to include) the `recipientIdNumbers` object in the response, the request would look like this: > /payout/v3?recipientIdNumbers.¤cy=EUR
To return (filter) only the payout with the specified `payoutRef` parameter, the request would look like this: > /payout/v3?payoutRef=dfbb8efc-6e85-4973-8f2e-69baf8624ae6
For a more detailed tutorial, see the [query parameters](doc:filtering-using-query-parameters) section of Guides. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - addressLine1 - addressLine2 - addressType - amount - batchRef - birthDate - city - country - countryOfBirth - countryOfNationality - currency - description - email - endDate - firstName - gender - governmentIdType - id - limit - mobileNumberCountry - offset - payoutAccountId - payoutProviderAdditionalRef - payoutProviderRef - payoutRef - payoutStatus - phoneNumber - phoneNumberCountry - postalCode - providerId - providerRecipientRef - providerResponse - providerType - recipientId - recipientIdNumbers - recipientIdNumbers.governmentId - recipientIdNumbers.passportId - recipientIdNumbers.employerId - recipientIdNumbers.driversLicenseId - recipientRef - region - startDate - transferStatus - updatedAt - userType - createdAt - lastName - mobileNumber - payoutDate ## Response parameters - offset - limit - rows - rows.batchRef - rows.id - rows.recipientRef - rows.recipientId - rows.payoutAccountId - rows.payoutRef - rows.providerId - rows.providerType - rows.payoutProviderRef - rows.payoutProviderAdditionalRef - rows.providerRecipientRef - rows.amount - rows.currency - rows.description - rows.payoutDate - rows.transferStatus - rows.payoutStatus - rows.providerResponse - rows.firstName - rows.lastName - rows.addressLine1 - rows.addressLine2 - rows.city - rows.region - rows.postalCode - rows.country - rows.email - rows.phoneNumber - rows.mobileNumber - rows.createdAt - rows.updatedAt - hasMore
- [View payouts pending](https://docs.nexiopay.com/reference/viewpayoutspending.md): Allows merchants to view all payouts to recipients that are in a pending status. Returns all payouts that meet the specified parameters (if any) and that are associated with the Nexio account used to [authenticate](doc:authentication). This is the only endpoint where you can use `payoutRef` in the request to view a specific payout based on that value. You may also request to return additional parameters and/or filter results using one or more [query parameters](doc:filtering-using-query-parameters). > ๐ Notes > > For example, to return (filter) all payouts where the currency is EUR and also (request to include) the `recipientIdNumbers` object in the response, the request would look like this: > /payout/v3?recipientIdNumbers.¤cy=EUR
To return (filter) only the payout with the specified `payoutRef` parameter, the request would look like this: > /payout/v3?payoutRef=dfbb8efc-6e85-4973-8f2e-69baf8624ae6
For a more detailed tutorial, see the [query parameters](doc:filtering-using-query-parameters) section of Guides. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Response parameters - offset - limit - rows - rows.id - rows.providerId - rows.batchRef - rows.recipientRef - rows.firstName - rows.lastName - rows.email - rows.currency - rows.amount - rows.country
- [Cancel pending payouts](https://docs.nexiopay.com/reference/cancelpendingpayouts.md): Allows merchants to cancel pending payout transactions. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - ids ## Response parameters - message
- [View payouts pending by ID](https://docs.nexiopay.com/reference/viewpayoutspendingbyid.md): Allows the merchant to view specific payout transactions that have a pending status by using the `payoutId` to filter results. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include the payout ID in the path parameter of the request. ## Request parameters - payoutId ## Response parameters - id - recipientId - payoutAccountId - recipientIdNumbers - recipientIdNumbers.governmentId - recipientIdNumbers.passportId - recipientIdNumbers.employerId - recipientIdNumbers.driversLicenseId - providerId - batchRef - payoutRef - recipientRef - firstName - lastName - email - amount - currency - country - providerType - createdAt - updatedAt - events - events.type - events.params - events.params.providerId
- [Submit payouts](https://docs.nexiopay.com/reference/submitpayouts-1.md): Allows you to submit one or more payouts in the body of an API request. Payouts can be made to existing recipients or you can create a recipient at the same time as submitting a payout by including the amount and currency for the payout as well as the required parameters for a recipient. ### Required payout parameters The required parameters for a payout are the following:
- `amount`
- `currency`
- The **required recipient parameters** ### Required recipient parameters For sending a payout to an **existing recipient**, you must specify one or more of the following recipient parameters (if you specify more than one, they are prioritized in the given order):
- `recipientRef`
- `recipientId`
- `email`
**Note:** The system ignores any other recipient parameters that you include.
For sending a payout to a **new recipient**, you must include at least the following recipient parameters:
- `recipientRef`
- `email`
- `firstName`
- `lastName`
- `country`
You may also optionally include any of the other parameters for [creating a recipient](ref:createrecipient). > ๐ Note > > For the payout provider Interchecks, if you pass a value for one of the `recipientIdNumbers` parameters when creating a new recipient, you cannot update any recipient information with [Update recipient](ref:updaterecipient) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include all the required parameters for a payout and a recipient, depending on whether this is for a new or existing recipient (see above). ## Request parameters - payouts - payouts.amount - payouts.currency - payouts.recipient - payouts.recipient.recipientRef - payouts.recipient.recipientId - payouts.recipient.email - payouts.recipient.firstName - payouts.recipient.lastName - payouts.recipient.country - payouts.recipient.providerId - payouts.recipient.userType - payouts.recipient.gender - payouts.recipient.birthDate - payouts.recipient.countryOfBirth - payouts.recipient.countryOfNationality - payouts.recipient.currency - payouts.recipient.addressType - payouts.recipient.addressLine1 - payouts.recipient.addressLine2 - payouts.recipient.city - payouts.recipient.region - payouts.recipient.postalCode - payouts.recipient.phoneNumber - payouts.recipient.phoneNumberCountry - payouts.recipient.mobileNumber - payouts.recipient.mobileNumberCountry - payouts.recipient.governmentIdType - payouts.recipient.recipientIdNumbers - payouts.recipient.recipientIdNumbers.governmentId - payouts.recipient.recipientIdNumbers.passportId - payouts.recipient.recipientIdNumbers.employerId - payouts.recipient.recipientIdNumbers.driversLicenseId - payouts.description - payouts.payoutRef - batchRef ## Response parameters - message
- [Submit payouts using batch file](https://docs.nexiopay.com/reference/payoutbatch-1.md): Allows you to submit one or more payouts using a batch file as input for the API request. Use this endpoint to make payouts to existing or new recipients. > ๐ Important > > Ensure the following for this endpoint:- The header content-type must be `multipart/form-data`.
- The batch file must be in a location that is accessible by the server making this API request.
> ๐ Note > > For the payout provider Interchecks, if you pass a value for one of the `recipientIdNumbers` parameters when creating a new recipient, you cannot update any recipient information with [Update recipient](ref:updaterecipient) endpoint. > โ ๏ธ Try It > > Due to technical limitations, it is not possible to use the Try It feature with this endpoint. Instead, use Postman or your own server (along with the credentials for your [Sandbox API user](doc:sandbox-environments)) to make the request. ## Batch file parameters The following table shows the required and optional parameters for making payouts using a batch file. For more information about each parameter, see the [Submit payouts](ref:submitpayouts) endpoint. To use your own field headers from your batch file, contact [Integrations Support](page:contact-us) for assistance. | Parameter | Name in batch file | Notes |
| batchRef | batchRef | If you include this parameter, the system only uses the first instance of it in the batch file. Other instances are ignored. If you want multiple batches to display as a single group in a report, specify the same value for each batch. Using this option allows you to easily view money sent to different payout providers so that you can properly fund those accounts. |
| currency | currency | Required for each payout. |
| amount | amount | Required for each payout. |
| description | description | Optional. |
| payoutRef | payoutRef | Optional. |
| recipient.recipientId | recipientId | Conditionally required for payout to an existing recipient when neither `recipientRef` nor `email` is included. This parameter is prioritized if more than one of those is included.
Not allowed for payout to a new recipient. |
| recipient.recipientRef | recipientRef | Conditionally required for payout to an existing recipient when neither `recipientId` nor `email` is included. This parameter is prioritized over email if that value is included. Otherwise, it is ignored if `recipientId` is included.
Required for payout to a new recipient.
Important: We strongly recommend that you include this value in your request instead of recipientId in order to facilitate payment reconciliation. |
| recipient.email | email | Conditionally required for payout to an existing recipient when neither `recipientId` nor `recipientRef` is included. This parameter is only prioritized if neither of the other two are included. Otherwise, it is ignored.
Required for payout to a new recipient. |
| recipient.firstName | firstName | Required for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.lastName | lastName | Required for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.country | country | Required for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.providerId | providerId | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.userType | userType | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.gender | gender | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.birthDate | birthDate | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.countryOfBirth | countryOfBirth | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.countryOfNationality | countryOfNationality | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.addressType | addressType | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.addressLine1 | addressLine1 | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.addressLine2 | addressLine2 | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.city | city | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.region | region | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.postalCode | postalCode | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.phoneNumber | phoneNumber | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.phoneNumberCountry | phoneNumberCountry | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.mobileNumber | mobileNumber | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.mobileNumberCountry | mobileNumberCountry | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
| recipient.governmentIdType | governmentIdType | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
governmentId (in recipient.recipientIdNumbers) | governmentId | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
passportId (in recipient.recipientIdNumbers) | passportId | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
driversLicenseId (in recipient.recipientIdNumbers) | driversLicenseId | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
employerId (in recipient.recipientIdNumbers) | employerId | Optional for payout to a new recipient.
Ignored for payout to an existing recipient. |
## Batch file format and examples The batch file needs to be in CSV format. The first line contains a comma-separated list of the parameters to use. Each subsequent line must have the same number of commas as the first line but does not have to have content for each parameter (except where the parameter is required for the payout request). For the possible required, conditionally required, and optional parameters to include, see the previous section. To use your own field headers from your batch file, contact [Integrations Support](page:contact-us) for assistance. ### Simple batch file example ``` firstName,lastName,recipientRef,email,country,amount,currency Yiseme,Gordman,9348rwf2,ygordman@testdata123.com,US,15,USD John,Johnson,123456r3,jj@123.com,CA,140,CAD ,,,,,, ``` [Download sample file (in ZIP)](https://drive.google.com/file/d/1rR_knD7aBeCUnTvbHATOrPsW5lsuz-BI/view?usp=sharing)
(To download, click the link and then select the option to "download".) ### Batch file with all parameters example ``` batchRef,currency,amount,description,payoutRef,recipientId,recipientRef,email,firstName,lastName,country,providerId,userType,gender,birthDate,countryOfBirth,countryOfNationality,addressType,addressLine1,addressLine2,city,region,postalCode,phoneNumber,phoneNumberCountry,mobileNumber,mobileNumberCountry,governmentIdType,governmentId,passportId,driversLicenseId,employerId batch006,USD,1314.27,June commission payment,113e9ee19a-9c5f-49ca-9a92-3e39e64219c01,98198452,DS1125345,recipientemail112@payoutnow.com,Judith,Callie,US,12695,INDIVIDUAL,FEMALE,12/5/90,US,US,RESIDENTIAL,123 Somewhere St,,Somewhere,AK,99885,801111111,US,8012222222,US,NATIONALIDCARD,999999999,,DL12343234, batch006,USD,125,June commission payment,Z12345 June 15th compensation pay1,98468985,Z11223456,recipientemai1l21@payoutnow.com,Merchnat,LLC,ES,12686,BUSINESS,MALE,11/19/91,ES,ES,BUSINESS,"C. del Pozo, 8",,Madrid,,28012,34915223894,ES,34915223895,ES,NATIONALIDCARD,,,,111111111 batch006,CAD,161.13,June commission payment,11a5ff4a13d4381,,RR12234346,recipientemail132@payoutnow.com,Wilimina,Manning,CA,12696,INDIVIDUAL,FEMALE,1/15/93,CA,CA,RESIDENTIAL,800 Benevenuto Ave,,Brentwood Bay,BC,V8M 1J8,2506524422,CA,2506524421,CA,PASSPORT,,789546512,, ``` [Download sample batch file (in ZIP)](https://drive.google.com/file/d/1JYmaQCyfQRy6ioMn5mZPVvFTGk2xgySC/view?usp=sharing)
(To download, click the link and then select the option to "download".)
- [View a payout](https://docs.nexiopay.com/reference/viewpayout-1.md): Searches for payouts with the given `payoutId`. > ๐ Note > > The `payoutId` parameter is not the same as the `payoutRef`, `payoutProviderRef`, or `payoutProviderAdditionalRef`. To view a payout using one of these other reference values, use the [View payouts](ref:viewpayouts) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include the payout ID in the path parameter of the request. ## Request parameters - payoutId ## Response parameters - batchRef - id - recipientRef - recipientId - payoutAccountId - payoutRef - providerId - providerType - payoutProviderRef - payoutProviderAdditionalRef - providerRecipientRef - amount - currency - description - payoutDate - transferStatus - payoutStatus - providerResponse - firstName - lastName - addressLine1 - addressLine2 - city - region - postalCode - country - email - phoneNumber - mobileNumber - createdAt - updatedAt
- [View payouts](https://docs.nexiopay.com/reference/viewpayouts-1.md): Returns all payouts that meet the specified parameters (if any) and that are associated with the Nexio account used to [authenticate](doc:authentication). This is the only endpoint where you can use `payoutRef` in the request to view a specific payout based on that value. You may also request to return additional parameters and/or filter results using one or more [query parameters](doc:filtering-using-query-parameters). > ๐ Notes > > By way of example, to return (filter) all payouts where the currency is EUR and also (request to include) the `recipientIdNumbers` object in the response, the request would look like this: > /payout/v3?recipientIdNumbers.¤cy=EUR
To return (filter) only the payout with the specified `payoutRef` parameter, the request would look like this: > /payout/v3?payoutRef=dfbb8efc-6e85-4973-8f2e-69baf8624ae6
For a more detailed tutorial, see the [query parameters](doc:filtering-using-query-parameters) section of Guides. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - addressLine1 - addressLine2 - addressType - amount - batchRef - birthDate - city - country - countryOfBirth - countryOfNationality - currency - description - email - endDate - firstName - gender - governmentIdType - id - limit - mobileNumberCountry - offset - payoutAccountId - payoutProviderAdditionalRef - payoutProviderRef - payoutRef - payoutStatus - phoneNumber - phoneNumberCountry - postalCode - providerId - providerRecipientRef - providerResponse - providerType - recipientId - recipientIdNumbers - recipientIdNumbers.governmentId - recipientIdNumbers.passportId - recipientIdNumbers.employerId - recipientIdNumbers.driversLicenseId - recipientRef - region - startDate - transferStatus - updatedAt - userType - createdAt - lastName - mobileNumber - payoutDate ## Response parameters - offset - limit - rows - rows.batchRef - rows.id - rows.recipientRef - rows.recipientId - rows.payoutAccountId - rows.payoutRef - rows.providerId - rows.providerType - rows.payoutProviderRef - rows.payoutProviderAdditionalRef - rows.providerRecipientRef - rows.amount - rows.currency - rows.description - rows.payoutDate - rows.transferStatus - rows.payoutStatus - rows.providerResponse - rows.firstName - rows.lastName - rows.addressLine1 - rows.addressLine2 - rows.city - rows.region - rows.postalCode - rows.country - rows.email - rows.phoneNumber - rows.mobileNumber - rows.createdAt - rows.updatedAt - hasMore
- [View payouts pending](https://docs.nexiopay.com/reference/viewpayoutspending-1.md): Allows merchants to view all payouts to recipients that are in a pending status. Returns all payouts that meet the specified parameters (if any) and that are associated with the Nexio account used to [authenticate](doc:authentication). This is the only endpoint where you can use `payoutRef` in the request to view a specific payout based on that value. You may also request to return additional parameters and/or filter results using one or more [query parameters](doc:filtering-using-query-parameters). > ๐ Notes > > For example, to return (filter) all payouts where the currency is EUR and also (request to include) the `recipientIdNumbers` object in the response, the request would look like this: > /payout/v3?recipientIdNumbers.¤cy=EUR
To return (filter) only the payout with the specified `payoutRef` parameter, the request would look like this: > /payout/v3?payoutRef=dfbb8efc-6e85-4973-8f2e-69baf8624ae6
For a more detailed tutorial, see the [query parameters](doc:filtering-using-query-parameters) section of Guides. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Response parameters - offset - limit - rows - rows.id - rows.providerId - rows.batchRef - rows.recipientRef - rows.firstName - rows.lastName - rows.email - rows.currency - rows.amount - rows.country
- [Cancel pending payouts](https://docs.nexiopay.com/reference/cancelpendingpayouts-1.md): Allows merchants to cancel pending payout transactions. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - ids ## Response parameters - message
- [View payouts pending by ID](https://docs.nexiopay.com/reference/viewpayoutspendingbyid-1.md): Allows the merchant to view specific payout transactions that have a pending status by using the `payoutId` to filter results. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include the payout ID in the path parameter of the request. ## Request parameters - payoutId ## Response parameters - id - recipientId - payoutAccountId - recipientIdNumbers - recipientIdNumbers.governmentId - recipientIdNumbers.passportId - recipientIdNumbers.employerId - recipientIdNumbers.driversLicenseId - providerId - batchRef - payoutRef - recipientRef - firstName - lastName - email - amount - currency - country - providerType - createdAt - updatedAt - events - events.type - events.params - events.params.providerId
- [Submit spendback](https://docs.nexiopay.com/reference/submitspendback.md): Allows you to submit a spendback in the body of an API request. A spendback request can only be made for an existing recipient and you can only process one spendback at a time. ### Required parameters Each spendback request must include the `amount` and `currency` parameters as well as one of the following recipient parameters (if you specify more than one, they are prioritized in the given order):
- `recipientId`
- `recipientRef`
- `email` > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include at least the `amount` and `currency` parameters, along with one of the recipient parameters (see above). ## Request parameters - recipientId - recipientRef - email - amount - currency - description - spendbackRef - providerId ## Response parameters - id - spendbackRef - recipientId - recipientRef - payoutAccountId - providerId - providerType - providerSpendbackRef - amount - currency - description - spendbackDate - spendbackStatus - providerResponse - createdAt - updatedAt
- [View spendbacks](https://docs.nexiopay.com/reference/viewspendbacks.md): Returns all spendbacks that meet the specified parameters (if any) and that are associated with the Nexio account used to [authenticate](doc:authentication). This is the only endpoint where you can use `spendbackRef` in the request to view a specific spendback based on that value. You may also request to filter results using one or more [query parameters](doc:filtering-using-query-parameters). > ๐ Notes > > For example, to return (filter) only the spendback with the specified `spendbackRef` parameter, the request would look like this: > /payout/v3/spendback?spendbackRef=43b57dce-4dca-474a-84f4-4684f3a8aa52
To return (filter) all spendbacks where the currency is EUR and there was an error response from the provider, the request would look like this: > /payout/v3/spendback?currency=EUR&spendbackStatus=90
For a more detailed tutorial, see the [query parameters](doc:filtering-using-query-parameters) section of Guides. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - amount - currency - description - endDate - id - limit - offset - payoutAccountId - providerId - providerResponse - providerSpendbackRef - providerType - recipientId - recipientRef - spendbackRef - spendbackStatus - startDate - updatedAt - createdAt - spendbackDate ## Response parameters - offset - limit - rows - rows.id - rows.spendbackRef - rows.recipientId - rows.recipientRef - rows.payoutAccountId - rows.providerId - rows.providerType - rows.providerSpendbackRef - rows.amount - rows.currency - rows.description - rows.spendbackDate - rows.spendbackStatus - rows.providerResponse - rows.createdAt - rows.updatedAt - hasMore
- [View a spendback](https://docs.nexiopay.com/reference/viewspendback.md): Searches for a spendback with the specified `spendbackId`. > ๐ Notes > > - The `spendbackId` parameter is not the same as the `spendbackRef` or `providerSpendbackRef`. > - To view a spendback using one of these other IDs, use the [View spendbacks](ref:viewspendbacks) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include the spendback ID in the path parameter of the request. ## Request parameters - spendbackId ## Response parameters - id - spendbackRef - recipientId - recipientRef - payoutAccountId - providerId - providerType - providerSpendbackRef - amount - currency - description - spendbackDate - spendbackStatus - providerResponse - createdAt - updatedAt
- [Spendback refund](https://docs.nexiopay.com/reference/spendbackrefund.md): Allows the merchant to refund recipients who have previously made a spendback transaction. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include at least the spendback ID and amount to refund in the request. ## Request parameters - spendbackId - amount - payoutAccountId - recipientId - providerId - spendbackRef - recipientRef - providerSpendbackRef - currency - providerType - spendbackType - spendbackStatus - spendbackDate - createdAt - updatedAt ## Response parameters - spendbackId - payoutAccountId - recipientId - providerId - spendbackRef - recipientRef - providerSpendbackRef - amount - currency - providerType - spendbackType - spendbackStatus - spendbackDate - createdAt - updatedAt
- [View recipient balance](https://docs.nexiopay.com/reference/recipientbalance.md): Allows merchants to view a recipient's spendback balance to ensure sufficient funds are available for spendbacks. Shows the balance for each spendback provider account associated with the `recipientRef` parameter. Requires `recipientRef` query parameter to access recipient balance information. This is the same `recipientRef` that is used in the [Submit spendback](ref:submitspendback) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include the `recipientRef` parameter in the request. ## Request parameters - recipientRef ## Response parameters - recipientRef - recipientBalances - recipientBalances.recipientId - recipientBalances.amount - recipientBalances.currency - recipientBalances.providerId - recipientBalances.providerType
- [Submit spendback](https://docs.nexiopay.com/reference/submitspendback-1.md): Allows you to submit a spendback in the body of an API request. A spendback request can only be made for an existing recipient and you can only process one spendback at a time. ### Required parameters Each spendback request must include the `amount` and `currency` parameters as well as one of the following recipient parameters (if you specify more than one, they are prioritized in the given order):
- `recipientId`
- `recipientRef`
- `email` > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include at least the `amount` and `currency` parameters, along with one of the recipient parameters (see above). ## Request parameters - recipientId - recipientRef - email - amount - currency - description - spendbackRef - providerId ## Response parameters - id - spendbackRef - recipientId - recipientRef - payoutAccountId - providerId - providerType - providerSpendbackRef - amount - currency - description - spendbackDate - spendbackStatus - providerResponse - createdAt - updatedAt
- [View spendbacks](https://docs.nexiopay.com/reference/viewspendbacks-1.md): Returns all spendbacks that meet the specified parameters (if any) and that are associated with the Nexio account used to [authenticate](doc:authentication). This is the only endpoint where you can use `spendbackRef` in the request to view a specific spendback based on that value. You may also request to filter results using one or more [query parameters](doc:filtering-using-query-parameters). > ๐ Notes > > For example, to return (filter) only the spendback with the specified `spendbackRef` parameter, the request would look like this: > /payout/v3/spendback?spendbackRef=43b57dce-4dca-474a-84f4-4684f3a8aa52
To return (filter) all spendbacks where the currency is EUR and there was an error response from the provider, the request would look like this: > /payout/v3/spendback?currency=EUR&spendbackStatus=90
For a more detailed tutorial, see the [query parameters](doc:filtering-using-query-parameters) section of Guides. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - amount - currency - description - endDate - id - limit - offset - payoutAccountId - providerId - providerResponse - providerSpendbackRef - providerType - recipientId - recipientRef - spendbackRef - spendbackStatus - startDate - updatedAt - createdAt - spendbackDate ## Response parameters - offset - limit - rows - rows.id - rows.spendbackRef - rows.recipientId - rows.recipientRef - rows.payoutAccountId - rows.providerId - rows.providerType - rows.providerSpendbackRef - rows.amount - rows.currency - rows.description - rows.spendbackDate - rows.spendbackStatus - rows.providerResponse - rows.createdAt - rows.updatedAt - hasMore
- [View a spendback](https://docs.nexiopay.com/reference/viewspendback-1.md): Searches for a spendback with the specified `spendbackId`. > ๐ Notes > > - The `spendbackId` parameter is not the same as the `spendbackRef` or `providerSpendbackRef`. > - To view a spendback using one of these other IDs, use the [View spendbacks](ref:viewspendbacks) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include the spendback ID in the path parameter of the request. ## Request parameters - spendbackId ## Response parameters - id - spendbackRef - recipientId - recipientRef - payoutAccountId - providerId - providerType - providerSpendbackRef - amount - currency - description - spendbackDate - spendbackStatus - providerResponse - createdAt - updatedAt
- [Spendback refund](https://docs.nexiopay.com/reference/spendbackrefund-1.md): Allows the merchant to refund recipients who have previously made a spendback transaction. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include at least the spendback ID and amount to refund in the request. ## Request parameters - spendbackId - amount - payoutAccountId - recipientId - providerId - spendbackRef - recipientRef - providerSpendbackRef - currency - providerType - spendbackType - spendbackStatus - spendbackDate - createdAt - updatedAt ## Response parameters - spendbackId - payoutAccountId - recipientId - providerId - spendbackRef - recipientRef - providerSpendbackRef - amount - currency - providerType - spendbackType - spendbackStatus - spendbackDate - createdAt - updatedAt
- [View recipient balance](https://docs.nexiopay.com/reference/recipientbalance-1.md): Allows merchants to view a recipient's spendback balance to ensure sufficient funds are available for spendbacks. Shows the balance for each spendback provider account associated with the `recipientRef` parameter. Requires `recipientRef` query parameter to access recipient balance information. This is the same `recipientRef` that is used in the [Submit spendback](ref:submitspendback) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include the `recipientRef` parameter in the request. ## Request parameters - recipientRef ## Response parameters - recipientRef - recipientBalances - recipientBalances.recipientId - recipientBalances.amount - recipientBalances.currency - recipientBalances.providerId - recipientBalances.providerType
- [View transaction by payment ID](https://docs.nexiopay.com/reference/viewtransactionpaymentid.md): Searches for transactions with the given payment ID. You get the payment ID in the [Run card transaction](ref:runcardtransaction) or [Process transaction from terminal](ref:processtransactionfromterminal) response as the `id`. Or, in the page event for the ecommerce or retail iframe. Because you get the `paymentId` in the response for a transaction, this endpoint is useful for quickly getting transaction information and updates. Also, you can use this endpoint instead of [View transactions](ref:viewtransactions) when you only need to get information about a single transaction and in order to get all response parameters related to the transaction without needing to request them specifically. > ๐ Notes > > - **It may take up to a minute after a transaction is run before you can see it in the response for this endpoint.** > - Payment ID is not the same as the Nexio Transaction ID, which is returned as `id` in this endpoint or in the [View transaction by transaction ID](ref:viewtransactiontransactionid) or [View transactions](ref:viewtransactions) endpoints. > - Certain transaction data will be returned as numerical values. The definitions are provided in the [Constant transaction values tables](doc:constant-transaction-values). > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include the payment ID in the path parameter of the request. ## Request parameters - paymentId ## Response parameters - id - merchantId - amount - transactionDate - transactionStatus - authCode - transactionType - cardType - cardNumber - cardHolder - processMethod - achDetailId - currencyId - reportDate - settledDate - capturedDate - originalTransactionId - createdAt - updatedAt - customer - customer.id - customer.firstName - customer.lastName - customer.postalCode - customer.phone - customer.email - customer.company - customer.customerRef - customer.transactionId - kount - kount.id - kount.status - kount.rules - kount.refNumber - kount.merc - kount.score - kount.ruleCount - kount.warningCount - kount.counterCount - kount.wasDeviceFingerprinted - kount.mode - kount.velo - kount.vmax - kount.transactionId - bankTransfer - bankTransfer.account - bankTransfer.checkNumber - bankTransfer.id - bankTransfer.routing - bankTransfer.transactionId - foreignProcessingCurrency - foreignProcessingCurrency.amount - foreignProcessingCurrency.currencyId - foreignProcessingCurrency.id - foreignProcessingCurrency.transactionId - threeDS - threeDS.id - threeDS.ECI - threeDS.type - threeDS.transactionId - gateway - gateway.gatewayName - gateway.refNumber - gateway.nsu - processor - processor.id - customerAddresses - customerAddresses.billingAddressOne - customerAddresses.billingAddressTwo - customerAddresses.billingCity - customerAddresses.billingCountry - customerAddresses.billingPhone - customerAddresses.billingPostal - customerAddresses.billingState - customerAddresses.shippingAddressOne - customerAddresses.shippingAddressTwo - customerAddresses.shippingCity - customerAddresses.shippingCountry - customerAddresses.shippingPhone - customerAddresses.shippingPostal - customerAddresses.shippingState - customerAddresses.id - customerAddresses.transactionId - subscription - subscription.id - subscription.accountId - subscription.initialBalance - subscription.interval - subscription.intervalCount - subscription.remainingBalance - subscription.scheduleType - subscription.subscriptionRef - subscription.transactionId - cardMetaData - cardMetaData.id - cardMetaData.bin - cardMetaData.cardBrand - cardMetaData.class - cardMetaData.countryCode - cardMetaData.currencyCode - cardMetaData.issuingBank - cardMetaData.transactionId - plugin - plugin.id - plugin.originalId - plugin.invoice - plugin.orderNumber - plugin.description - plugin.pluginType - plugin.paymentOptionTag - plugin.transactionId - transactionDetails - transactionDetails.id - transactionDetails.clientIp - transactionDetails.customFields - transactionDetails.description - transactionDetails.installments - transactionDetails.installmentUnit - transactionDetails.paymentType - transactionDetails.retryCount - transactionDetails.shoppingCart - transactionDetails.userName - transactionDetails.transactionId - linkedChargebackId
- [View transaction by transaction ID](https://docs.nexiopay.com/reference/viewtransactiontransactionid.md): Searches for transactions with the given transaction ID. You get the transaction ID in the [webhook](doc:webhook-body-examples#transaction-eventtype) with the `transactionId` (note that this parameter is not returned for legacy webhooks) or in the `id` returned in this endpoint or in the [View transaction by payment ID](ref:viewtransactionpaymentid) or [View transactions](ref:viewtransactions) endpoints. You can use this endpoint instead of [View transactions](ref:viewtransactions) when you only need to get information about a single transaction and in order to get all response parameters related to the transaction without needing to request them specifically. > ๐ Notes > > - **It may take up to a minute after a transaction is run before you can see it in the response for this endpoint.** > - Transaction ID is not the same as the Nexio Payment ID, which is returned as `id` in the [Run card transaction](ref:runcardtransaction) response. > - Certain transaction data will be returned as numerical values. The definitions are provided in the [Constant transaction values tables](doc:constant-transaction-values). > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include the transaction ID in the path parameter of the request. ## Request parameters - transactionId ## Response parameters - id - merchantId - amount - transactionDate - transactionStatus - authCode - transactionType - cardType - cardNumber - cardHolder - processMethod - achDetailId - currencyId - reportDate - settledDate - capturedDate - originalTransactionId - createdAt - updatedAt - customer - customer.id - customer.firstName - customer.lastName - customer.postalCode - customer.phone - customer.email - customer.company - customer.customerRef - customer.transactionId - kount - kount.id - kount.status - kount.rules - kount.refNumber - kount.merc - kount.score - kount.ruleCount - kount.warningCount - kount.counterCount - kount.wasDeviceFingerprinted - kount.mode - kount.velo - kount.vmax - kount.transactionId - bankTransfer - bankTransfer.account - bankTransfer.checkNumber - bankTransfer.id - bankTransfer.routing - bankTransfer.transactionId - foreignProcessingCurrency - foreignProcessingCurrency.amount - foreignProcessingCurrency.currencyId - foreignProcessingCurrency.id - foreignProcessingCurrency.transactionId - threeDS - threeDS.id - threeDS.ECI - threeDS.type - threeDS.transactionId - gateway - gateway.gatewayName - gateway.refNumber - gateway.nsu - processor - processor.id - customerAddresses - customerAddresses.billingAddressOne - customerAddresses.billingAddressTwo - customerAddresses.billingCity - customerAddresses.billingCountry - customerAddresses.billingPhone - customerAddresses.billingPostal - customerAddresses.billingState - customerAddresses.shippingAddressOne - customerAddresses.shippingAddressTwo - customerAddresses.shippingCity - customerAddresses.shippingCountry - customerAddresses.shippingPhone - customerAddresses.shippingPostal - customerAddresses.shippingState - customerAddresses.id - customerAddresses.transactionId - subscription - subscription.id - subscription.accountId - subscription.initialBalance - subscription.interval - subscription.intervalCount - subscription.remainingBalance - subscription.scheduleType - subscription.subscriptionRef - subscription.transactionId - cardMetaData - cardMetaData.id - cardMetaData.bin - cardMetaData.cardBrand - cardMetaData.class - cardMetaData.countryCode - cardMetaData.currencyCode - cardMetaData.issuingBank - cardMetaData.transactionId - plugin - plugin.id - plugin.originalId - plugin.invoice - plugin.orderNumber - plugin.description - plugin.userId - plugin.pluginType - plugin.paymentOptionTag - plugin.transactionId - transactionDetails - transactionDetails.id - transactionDetails.clientIp - transactionDetails.customFields - transactionDetails.description - transactionDetails.installments - transactionDetails.installmentUnit - transactionDetails.paymentType - transactionDetails.retryCount - transactionDetails.shoppingCart - transactionDetails.userName - transactionDetails.transactionId - linkedChargebackId
- [View transactions](https://docs.nexiopay.com/reference/viewtransactions.md): The endpoint returns all transactions that meet the specified parameters and that are associated with the Nexio account used to [authenticate](doc:authentication). You request (or filter) on fields of the query parameters as in the following example: /transaction/v3?kount.&plugin.&customer.&processor.&gateway. See the [Finding a transaction](doc:finding-a-transaction) topic in Guides for a full tutorial. The default response only includes a small number of parameters. If you want additional objects and parameters, you must specify them in the request. For more information about how to do this, see the [Requesting additional response parameters](doc:requesting-additional-response-parameters) topic in Guides. > ๐ Warning > > You must specify at least one parameter. Failing to submit one results in an Internal Server Error. Also, it is **not** possible to send a request with all parameters. Doing so results in a 400 error and the system does not return a response. > ๐ Notes > > - **It may take up to a minute after a transaction is run before you can see it in the response for this endpoint.** > - If you want to search for a transaction by `paymentId`, you should use the [View transaction by payment ID](ref:viewtransactionpaymentid) endpoint so that you get all the details for the transaction. Alternately, include the value of the `paymentId` in the `plugin.originalId` query parameter in this endpoint along with any [additional response parameters](doc:requesting-additional-response-parameters). > - If you want to search for a transaction by `transactionId`, you should use the [View transaction by transaction ID](ref:viewtransactiontransactionid) endpoint so that you get all the details for the transaction. Alternately, include the transaction ID value in the `id` or `transactionId` (within any object) query parameter in this endpoint along with any [additional response parameters](doc:requesting-additional-response-parameters). > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
When you use the test account, in order to avoid potential security issues, the system returns a set of test transactions. No other transactions that you may have run previously display in the results. ## Request parameters - achDetailId - amount - authCode - bankTransfer - bankTransfer.account - bankTransfer.checkNumber - bankTransfer.id - bankTransfer.routing - bankTransfer.transactionId - capturedDate - cardNumber - cardHolder - cardType - createdAt - currencyId - customer - customer.company - customer.customerRef - customer.email - customer.firstName - customer.id - customer.lastName - customer.postalCode - customer.phone - customer.transactionId - customerAddresses - customerAddresses.billingAddressOne - customerAddresses.billingAddressTwo - customerAddresses.billingCity - customerAddresses.billingCountry - customerAddresses.billingPhone - customerAddresses.billingPostalCode - customerAddresses.billingState - customerAddresses.shippingAddressOne - customerAddresses.shippingAddressTwo - customerAddresses.shippingCity - customerAddresses.shippingCountry - customerAddresses.shippingPhone - customerAddresses.shippingPostalCode - customerAddresses.shippingState - customerAddresses.id - customerAddresses.transactionId - endDate - foreignProcessingCurrency - foreignProcessingCurrency.amount - foreignProcessingCurrency.currencyId - foreignProcessingCurrency.id - foreignProcessingCurrency.transactionId - gateway - gateway.additionalRefNumber - gateway.batchRef - gateway.gatewayType - gateway.id - gateway.merchantId - gateway.message - gateway.trackingCode - gateway.refNumber - gateway.transactionId - gateway.nsu - id - kount - kount.counterCount - kount.id - kount.merc - kount.mode - kount.refNumber - kount.ruleCount - kount.rules - kount.score - kount.status - kount.transactionId - kount.velo - kount.vmax - kount.warningCount - kount.wasDeviceFingerprinted - linkedChargebackId - merchantIds - originalTransactionId - plugin - plugin.description - plugin.id - plugin.invoice - plugin.orderNumber - plugin.originalId - plugin.paymentOptionTag - plugin.pluginType - plugin.transactionId - plugin.userId - processMethod - processor - processor.batchRef - processor.id - processor.originalId - processor.processorType - processor.transactionId - processor.transactionRef - reportDate - settledDate - startDate - subscription - subscription.accountId - subscription.id - subscription.initialBalance - subscription.interval - subscription.intervalCount - subscription.remainingBalance - subscription.scheduleType - subscription.subscriptionRef - subscription.transactionId - transactionDate - transactionDetails - transactionDetails.clientIp - transactionDetails.customFields - transactionDetails.description - transactionDetails.id - transactionDetails.paymentType - transactionDetails.retryCount - transactionDetails.shoppingCart - transactionDetails.transactionId - transactionDetails.userName - transactionStatus - transactionType - updatedAt - limit - offset ## Response parameters - offset - limit - rows - rows.id - rows.merchantId - rows.amount - rows.transactionDate - rows.transactionStatus - rows.authCode - rows.transactionType - rows.cardType - rows.cardNumber - rows.cardHolder - rows.processMethod - rows.achDetailId - rows.currencyId - rows.reportDate - rows.settledDate - rows.capturedDate - rows.originalTransactionId - rows.createdAt - rows.updatedAt - rows.customer - rows.customer.id - rows.customer.firstName - rows.customer.lastName - rows.customer.postalCode - rows.customer.phone - rows.customer.email - rows.customer.company - rows.customer.customerRef - rows.customer.transactionId - rows.kount - rows.kount.id - rows.kount.status - rows.kount.rules - rows.kount.refNumber - rows.kount.merc - rows.kount.score - rows.kount.ruleCount - rows.kount.warningCount - rows.kount.counterCount - rows.kount.wasDeviceFingerprinted - rows.kount.mode - rows.kount.velo - rows.kount.vmax - rows.kount.transactionId - rows.bankTransfer - rows.bankTransfer.account - rows.bankTransfer.checkNumber - rows.bankTransfer.id - rows.bankTransfer.routing - rows.bankTransfer.transactionId - rows.foreignProcessingCurrency - rows.foreignProcessingCurrency.amount - rows.foreignProcessingCurrency.currencyId - rows.foreignProcessingCurrency.id - rows.foreignProcessingCurrency.transactionId - rows.threeDS - rows.threeDS.id - rows.threeDS.ECI - rows.threeDS.type - rows.threeDS.transactionId - rows.gateway - rows.gateway.gatewayName - rows.gateway.refNumber - rows.gateway.nsu - rows.processor - rows.processor.id - rows.customerAddresses - rows.customerAddresses.billingAddressOne - rows.customerAddresses.billingAddressTwo - rows.customerAddresses.billingCity - rows.customerAddresses.billingCountry - rows.customerAddresses.billingPhone - rows.customerAddresses.billingPostal - rows.customerAddresses.billingState - rows.customerAddresses.shippingAddressOne - rows.customerAddresses.shippingAddressTwo - rows.customerAddresses.shippingCity - rows.customerAddresses.shippingCountry - rows.customerAddresses.shippingPhone - rows.customerAddresses.shippingPostal - rows.customerAddresses.shippingState - rows.customerAddresses.id - rows.customerAddresses.transactionId - rows.subscription - rows.subscription.id - rows.subscription.accountId - rows.subscription.initialBalance - rows.subscription.interval - rows.subscription.intervalCount - rows.subscription.remainingBalance - rows.subscription.scheduleType - rows.subscription.subscriptionRef - rows.subscription.transactionId - rows.cardMetaData - rows.cardMetaData.id - rows.cardMetaData.bin - rows.cardMetaData.cardBrand - rows.cardMetaData.class - rows.cardMetaData.countryCode - rows.cardMetaData.currencyCode - rows.cardMetaData.issuingBank - rows.cardMetaData.transactionId - rows.plugin - rows.plugin.id - rows.plugin.originalId - rows.plugin.invoice - rows.plugin.orderNumber - rows.plugin.description - rows.plugin.pluginType - rows.plugin.paymentOptionTag - rows.plugin.transactionId - rows.transactionDetails - rows.transactionDetails.id - rows.transactionDetails.clientIp - rows.transactionDetails.customFields - rows.transactionDetails.description - rows.transactionDetails.installments - rows.transactionDetails.installmentUnit - rows.transactionDetails.paymentType - rows.transactionDetails.retryCount - rows.transactionDetails.shoppingCart - rows.transactionDetails.userName - rows.transactionDetails.transactionId - hasMore
- [View transaction count](https://docs.nexiopay.com/reference/viewtransactioncount.md): Returns a count of all transactions between the default or specified date range. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - endDate - startDate ## Response parameters - integer
- [View transaction total](https://docs.nexiopay.com/reference/viewtransactiontotal.md): Returns a sum of the transaction amounts between the given dates. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - endDate - startDate ## Response parameters - number
- [View daily transaction summary](https://docs.nexiopay.com/reference/viewdailytransactionsummary.md): Returns transaction summaries per hour for the given date and the day before that. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - date ## Response parameters - today - today.hour - today.amount - today.count - yesterday - yesterday.hour - yesterday.amount - yesterday.count
- [View transactions summary](https://docs.nexiopay.com/reference/viewtransactionsummary.md): Returns a summary (total transaction amount, month, and merchant ID) for the month's transactions between the specified start and end dates for each merchant account associated with the API user. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - endDate - startDate ## Response parameters - amount - transactionDate - merchantId
- [View card types](https://docs.nexiopay.com/reference/viewcardtypes.md): Returns an array listing all possible card types for transactions in Nexio. See also the [Card type (cardType)](doc:constant-transaction-values#card-type-cardtype) section of "Constant transaction values" in Guides. > ๐ Note > > It is not possible to use this endpoint to see the possible card types that your merchant account can accept. That is dependent on the [connections](doc:connections) that you have for your account. > > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Response parameters - id - name
- [View transaction by payment ID](https://docs.nexiopay.com/reference/viewtransactionpaymentid-1.md): Searches for transactions with the given payment ID. You get the payment ID in the [Run card transaction](ref:runcardtransaction) or [Process transaction from terminal](ref:processtransactionfromterminal) response as the `id`. Or, in the page event for the ecommerce or retail iframe. Because you get the `paymentId` in the response for a transaction, this endpoint is useful for quickly getting transaction information and updates. Also, you can use this endpoint instead of [View transactions](ref:viewtransactions) when you only need to get information about a single transaction and in order to get all response parameters related to the transaction without needing to request them specifically. > ๐ Notes > > - **It may take up to a minute after a transaction is run before you can see it in the response for this endpoint.** > - Payment ID is not the same as the Nexio Transaction ID, which is returned as `id` in this endpoint or in the [View transaction by transaction ID](ref:viewtransactiontransactionid) or [View transactions](ref:viewtransactions) endpoints. > - Certain transaction data will be returned as numerical values. The definitions are provided in the [Constant transaction values tables](doc:constant-transaction-values). > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include the payment ID in the path parameter of the request. ## Request parameters - paymentId ## Response parameters - id - merchantId - amount - transactionDate - transactionStatus - authCode - transactionType - cardType - cardNumber - cardHolder - processMethod - achDetailId - currencyId - reportDate - settledDate - capturedDate - originalTransactionId - createdAt - updatedAt - customer - customer.id - customer.firstName - customer.lastName - customer.postalCode - customer.phone - customer.email - customer.company - customer.customerRef - customer.transactionId - kount - kount.id - kount.status - kount.rules - kount.refNumber - kount.merc - kount.score - kount.ruleCount - kount.warningCount - kount.counterCount - kount.wasDeviceFingerprinted - kount.mode - kount.velo - kount.vmax - kount.transactionId - bankTransfer - bankTransfer.account - bankTransfer.checkNumber - bankTransfer.id - bankTransfer.routing - bankTransfer.transactionId - foreignProcessingCurrency - foreignProcessingCurrency.amount - foreignProcessingCurrency.currencyId - foreignProcessingCurrency.id - foreignProcessingCurrency.transactionId - threeDS - threeDS.id - threeDS.ECI - threeDS.type - threeDS.transactionId - gateway - gateway.gatewayName - gateway.refNumber - gateway.nsu - processor - processor.id - customerAddresses - customerAddresses.billingAddressOne - customerAddresses.billingAddressTwo - customerAddresses.billingCity - customerAddresses.billingCountry - customerAddresses.billingPhone - customerAddresses.billingPostal - customerAddresses.billingState - customerAddresses.shippingAddressOne - customerAddresses.shippingAddressTwo - customerAddresses.shippingCity - customerAddresses.shippingCountry - customerAddresses.shippingPhone - customerAddresses.shippingPostal - customerAddresses.shippingState - customerAddresses.id - customerAddresses.transactionId - subscription - subscription.id - subscription.accountId - subscription.initialBalance - subscription.interval - subscription.intervalCount - subscription.remainingBalance - subscription.scheduleType - subscription.subscriptionRef - subscription.transactionId - cardMetaData - cardMetaData.id - cardMetaData.bin - cardMetaData.cardBrand - cardMetaData.class - cardMetaData.countryCode - cardMetaData.currencyCode - cardMetaData.issuingBank - cardMetaData.transactionId - plugin - plugin.id - plugin.originalId - plugin.invoice - plugin.orderNumber - plugin.description - plugin.pluginType - plugin.paymentOptionTag - plugin.transactionId - transactionDetails - transactionDetails.id - transactionDetails.clientIp - transactionDetails.customFields - transactionDetails.description - transactionDetails.installments - transactionDetails.installmentUnit - transactionDetails.paymentType - transactionDetails.retryCount - transactionDetails.shoppingCart - transactionDetails.userName - transactionDetails.transactionId - linkedChargebackId
- [View transaction by transaction ID](https://docs.nexiopay.com/reference/viewtransactiontransactionid-1.md): Searches for transactions with the given transaction ID. You get the transaction ID in the [webhook](doc:webhook-body-examples#transaction-eventtype) with the `transactionId` (note that this parameter is not returned for legacy webhooks) or in the `id` returned in this endpoint or in the [View transaction by payment ID](ref:viewtransactionpaymentid) or [View transactions](ref:viewtransactions) endpoints. You can use this endpoint instead of [View transactions](ref:viewtransactions) when you only need to get information about a single transaction and in order to get all response parameters related to the transaction without needing to request them specifically. > ๐ Notes > > - **It may take up to a minute after a transaction is run before you can see it in the response for this endpoint.** > - Transaction ID is not the same as the Nexio Payment ID, which is returned as `id` in the [Run card transaction](ref:runcardtransaction) response. > - Certain transaction data will be returned as numerical values. The definitions are provided in the [Constant transaction values tables](doc:constant-transaction-values). > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
Include the transaction ID in the path parameter of the request. ## Request parameters - transactionId ## Response parameters - id - merchantId - amount - transactionDate - transactionStatus - authCode - transactionType - cardType - cardNumber - cardHolder - processMethod - achDetailId - currencyId - reportDate - settledDate - capturedDate - originalTransactionId - createdAt - updatedAt - customer - customer.id - customer.firstName - customer.lastName - customer.postalCode - customer.phone - customer.email - customer.company - customer.customerRef - customer.transactionId - kount - kount.id - kount.status - kount.rules - kount.refNumber - kount.merc - kount.score - kount.ruleCount - kount.warningCount - kount.counterCount - kount.wasDeviceFingerprinted - kount.mode - kount.velo - kount.vmax - kount.transactionId - bankTransfer - bankTransfer.account - bankTransfer.checkNumber - bankTransfer.id - bankTransfer.routing - bankTransfer.transactionId - foreignProcessingCurrency - foreignProcessingCurrency.amount - foreignProcessingCurrency.currencyId - foreignProcessingCurrency.id - foreignProcessingCurrency.transactionId - threeDS - threeDS.id - threeDS.ECI - threeDS.type - threeDS.transactionId - gateway - gateway.gatewayName - gateway.refNumber - gateway.nsu - processor - processor.id - customerAddresses - customerAddresses.billingAddressOne - customerAddresses.billingAddressTwo - customerAddresses.billingCity - customerAddresses.billingCountry - customerAddresses.billingPhone - customerAddresses.billingPostal - customerAddresses.billingState - customerAddresses.shippingAddressOne - customerAddresses.shippingAddressTwo - customerAddresses.shippingCity - customerAddresses.shippingCountry - customerAddresses.shippingPhone - customerAddresses.shippingPostal - customerAddresses.shippingState - customerAddresses.id - customerAddresses.transactionId - subscription - subscription.id - subscription.accountId - subscription.initialBalance - subscription.interval - subscription.intervalCount - subscription.remainingBalance - subscription.scheduleType - subscription.subscriptionRef - subscription.transactionId - cardMetaData - cardMetaData.id - cardMetaData.bin - cardMetaData.cardBrand - cardMetaData.class - cardMetaData.countryCode - cardMetaData.currencyCode - cardMetaData.issuingBank - cardMetaData.transactionId - plugin - plugin.id - plugin.originalId - plugin.invoice - plugin.orderNumber - plugin.description - plugin.userId - plugin.pluginType - plugin.paymentOptionTag - plugin.transactionId - transactionDetails - transactionDetails.id - transactionDetails.clientIp - transactionDetails.customFields - transactionDetails.description - transactionDetails.installments - transactionDetails.installmentUnit - transactionDetails.paymentType - transactionDetails.retryCount - transactionDetails.shoppingCart - transactionDetails.userName - transactionDetails.transactionId - linkedChargebackId
- [View transactions](https://docs.nexiopay.com/reference/viewtransactions-1.md): The endpoint returns all transactions that meet the specified parameters and that are associated with the Nexio account used to [authenticate](doc:authentication). You request (or filter) on fields of the query parameters as in the following example: /transaction/v3?kount.&plugin.&customer.&processor.&gateway. See the [Finding a transaction](doc:finding-a-transaction) topic in Guides for a full tutorial. The default response only includes a small number of parameters. If you want additional objects and parameters, you must specify them in the request. For more information about how to do this, see the [Requesting additional response parameters](doc:requesting-additional-response-parameters) topic in Guides. > ๐ Warning > > You must specify at least one parameter. Failing to submit one results in an Internal Server Error. Also, it is **not** possible to send a request with all parameters. Doing so results in a 400 error and the system does not return a response. > ๐ Notes > > - **It may take up to a minute after a transaction is run before you can see it in the response for this endpoint.** > - If you want to search for a transaction by `paymentId`, you should use the [View transaction by payment ID](ref:viewtransactionpaymentid) endpoint so that you get all the details for the transaction. Alternately, include the value of the `paymentId` in the `plugin.originalId` query parameter in this endpoint along with any [additional response parameters](doc:requesting-additional-response-parameters). > - If you want to search for a transaction by `transactionId`, you should use the [View transaction by transaction ID](ref:viewtransactiontransactionid) endpoint so that you get all the details for the transaction. Alternately, include the transaction ID value in the `id` or `transactionId` (within any object) query parameter in this endpoint along with any [additional response parameters](doc:requesting-additional-response-parameters). > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right. > username: `docs@nexiopay.com` > password: `JZdzoXpdDeH6VA`
When you use the test account, in order to avoid potential security issues, the system returns a set of test transactions. No other transactions that you may have run previously display in the results. ## Request parameters - achDetailId - amount - authCode - bankTransfer - bankTransfer.account - bankTransfer.checkNumber - bankTransfer.id - bankTransfer.routing - bankTransfer.transactionId - capturedDate - cardNumber - cardHolder - cardType - createdAt - currencyId - customer - customer.company - customer.customerRef - customer.email - customer.firstName - customer.id - customer.lastName - customer.postalCode - customer.phone - customer.transactionId - customerAddresses - customerAddresses.billingAddressOne - customerAddresses.billingAddressTwo - customerAddresses.billingCity - customerAddresses.billingCountry - customerAddresses.billingPhone - customerAddresses.billingPostalCode - customerAddresses.billingState - customerAddresses.shippingAddressOne - customerAddresses.shippingAddressTwo - customerAddresses.shippingCity - customerAddresses.shippingCountry - customerAddresses.shippingPhone - customerAddresses.shippingPostalCode - customerAddresses.shippingState - customerAddresses.id - customerAddresses.transactionId - endDate - foreignProcessingCurrency - foreignProcessingCurrency.amount - foreignProcessingCurrency.currencyId - foreignProcessingCurrency.id - foreignProcessingCurrency.transactionId - gateway - gateway.additionalRefNumber - gateway.batchRef - gateway.gatewayType - gateway.id - gateway.merchantId - gateway.message - gateway.trackingCode - gateway.refNumber - gateway.transactionId - gateway.nsu - id - kount - kount.counterCount - kount.id - kount.merc - kount.mode - kount.refNumber - kount.ruleCount - kount.rules - kount.score - kount.status - kount.transactionId - kount.velo - kount.vmax - kount.warningCount - kount.wasDeviceFingerprinted - linkedChargebackId - merchantIds - originalTransactionId - plugin - plugin.description - plugin.id - plugin.invoice - plugin.orderNumber - plugin.originalId - plugin.paymentOptionTag - plugin.pluginType - plugin.transactionId - plugin.userId - processMethod - processor - processor.batchRef - processor.id - processor.originalId - processor.processorType - processor.transactionId - processor.transactionRef - reportDate - settledDate - startDate - subscription - subscription.accountId - subscription.id - subscription.initialBalance - subscription.interval - subscription.intervalCount - subscription.remainingBalance - subscription.scheduleType - subscription.subscriptionRef - subscription.transactionId - transactionDate - transactionDetails - transactionDetails.clientIp - transactionDetails.customFields - transactionDetails.description - transactionDetails.id - transactionDetails.paymentType - transactionDetails.retryCount - transactionDetails.shoppingCart - transactionDetails.transactionId - transactionDetails.userName - transactionStatus - transactionType - updatedAt - limit - offset ## Response parameters - offset - limit - rows - rows.id - rows.merchantId - rows.amount - rows.transactionDate - rows.transactionStatus - rows.authCode - rows.transactionType - rows.cardType - rows.cardNumber - rows.cardHolder - rows.processMethod - rows.achDetailId - rows.currencyId - rows.reportDate - rows.settledDate - rows.capturedDate - rows.originalTransactionId - rows.createdAt - rows.updatedAt - rows.customer - rows.customer.id - rows.customer.firstName - rows.customer.lastName - rows.customer.postalCode - rows.customer.phone - rows.customer.email - rows.customer.company - rows.customer.customerRef - rows.customer.transactionId - rows.kount - rows.kount.id - rows.kount.status - rows.kount.rules - rows.kount.refNumber - rows.kount.merc - rows.kount.score - rows.kount.ruleCount - rows.kount.warningCount - rows.kount.counterCount - rows.kount.wasDeviceFingerprinted - rows.kount.mode - rows.kount.velo - rows.kount.vmax - rows.kount.transactionId - rows.bankTransfer - rows.bankTransfer.account - rows.bankTransfer.checkNumber - rows.bankTransfer.id - rows.bankTransfer.routing - rows.bankTransfer.transactionId - rows.foreignProcessingCurrency - rows.foreignProcessingCurrency.amount - rows.foreignProcessingCurrency.currencyId - rows.foreignProcessingCurrency.id - rows.foreignProcessingCurrency.transactionId - rows.threeDS - rows.threeDS.id - rows.threeDS.ECI - rows.threeDS.type - rows.threeDS.transactionId - rows.gateway - rows.gateway.gatewayName - rows.gateway.refNumber - rows.gateway.nsu - rows.processor - rows.processor.id - rows.customerAddresses - rows.customerAddresses.billingAddressOne - rows.customerAddresses.billingAddressTwo - rows.customerAddresses.billingCity - rows.customerAddresses.billingCountry - rows.customerAddresses.billingPhone - rows.customerAddresses.billingPostal - rows.customerAddresses.billingState - rows.customerAddresses.shippingAddressOne - rows.customerAddresses.shippingAddressTwo - rows.customerAddresses.shippingCity - rows.customerAddresses.shippingCountry - rows.customerAddresses.shippingPhone - rows.customerAddresses.shippingPostal - rows.customerAddresses.shippingState - rows.customerAddresses.id - rows.customerAddresses.transactionId - rows.subscription - rows.subscription.id - rows.subscription.accountId - rows.subscription.initialBalance - rows.subscription.interval - rows.subscription.intervalCount - rows.subscription.remainingBalance - rows.subscription.scheduleType - rows.subscription.subscriptionRef - rows.subscription.transactionId - rows.cardMetaData - rows.cardMetaData.id - rows.cardMetaData.bin - rows.cardMetaData.cardBrand - rows.cardMetaData.class - rows.cardMetaData.countryCode - rows.cardMetaData.currencyCode - rows.cardMetaData.issuingBank - rows.cardMetaData.transactionId - rows.plugin - rows.plugin.id - rows.plugin.originalId - rows.plugin.invoice - rows.plugin.orderNumber - rows.plugin.description - rows.plugin.pluginType - rows.plugin.paymentOptionTag - rows.plugin.transactionId - rows.transactionDetails - rows.transactionDetails.id - rows.transactionDetails.clientIp - rows.transactionDetails.customFields - rows.transactionDetails.description - rows.transactionDetails.installments - rows.transactionDetails.installmentUnit - rows.transactionDetails.paymentType - rows.transactionDetails.retryCount - rows.transactionDetails.shoppingCart - rows.transactionDetails.userName - rows.transactionDetails.transactionId - hasMore
- [View transaction count](https://docs.nexiopay.com/reference/viewtransactioncount-1.md): Returns a count of all transactions between the default or specified date range. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - endDate - startDate ## Response parameters - integer
- [View transaction total](https://docs.nexiopay.com/reference/viewtransactiontotal-1.md): Returns a sum of the transaction amounts between the given dates. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - endDate - startDate ## Response parameters - number
- [View daily transaction summary](https://docs.nexiopay.com/reference/viewdailytransactionsummary-1.md): Returns transaction summaries per hour for the given date and the day before that. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - date ## Response parameters - today - today.hour - today.amount - today.count - yesterday - yesterday.hour - yesterday.amount - yesterday.count
- [View transactions summary](https://docs.nexiopay.com/reference/viewtransactionsummary-1.md): Returns a summary (total transaction amount, month, and merchant ID) for the month's transactions between the specified start and end dates for each merchant account associated with the API user. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - endDate - startDate ## Response parameters - amount - transactionDate - merchantId
- [View card types](https://docs.nexiopay.com/reference/viewcardtypes-1.md): Returns an array listing all possible card types for transactions in Nexio. See also the [Card type (cardType)](doc:constant-transaction-values#card-type-cardtype) section of "Constant transaction values" in Guides. > ๐ Note > > It is not possible to use this endpoint to see the possible card types that your merchant account can accept. That is dependent on the [connections](doc:connections) that you have for your account. > > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Response parameters - id - name
- [View recoveries](https://docs.nexiopay.com/reference/viewrecoverystatus.md): Returns declined transactions within the given date range along with the [decline recovery](doc:constant-transaction-values#recovery-status-recoverystatus) status of each. For additional information about this endpoint, see the [Retrieving transaction list from decline recovery](doc:retrieving-transaction-list-from-decline-recovery) tutorial. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - endDate - limit - offset - startDate - recoveryStatus ## Response parameters - offset - limit - rows - rows.id - rows.retryDate - rows.transactionDate - rows.originalAmount - rows.originalDeclinePaymentId - rows.orderNumber - rows.recoveryStatus - rows.retryCount - rows.merchantId - rows.userName - rows.isEnabledForRecovery - rows.declineMessage - rows.updatedAt - hasMore
- [View a recovery](https://docs.nexiopay.com/reference/viewrecovery.md): Returns a single decline recovery transaction. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include the retry ID in the path parameter of the request. ## Request parameters - retryId ## Response parameters - id - cardToken - retryDate - transactionDate - originalAmount - originalDeclinePaymentId - retryEngineType - retryProviderRefNumber - orderNumber - recoveryStatus - retryCount - merchantId - originalPaymentRequest - retryMetadata - userName - isEnabledForRecovery - retryProviderBody - declineMessage - createdAt - updatedAt
- [Enable or disable retries for a single transaction](https://docs.nexiopay.com/reference/enableordisableretriesforasingletransaction.md): Allows the merchant to enable or disable retries for a single transaction when that transaction is declined. For more information, see the [Decline recovery overview](doc:decline-recovery-overview). > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include at least the retry ID in the body of the request. ## Request parameters - id - isEnabledForRecovery ## Response parameters - id - isEnabledForRecovery - success
- [Enable or disable retries for multiple transactions](https://docs.nexiopay.com/reference/enableordisableretriesformultipletransactions.md): Allows the merchant to enable or disable retries for multiple transactions when those transactions are declined. For more information, see the [Decline recovery overview](doc:decline-recovery-overview). > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include at minumum one or more retry IDs in an array in the body of the request. ## Request parameters - retries - retries.id - retries.isEnabledForRecovery ## Response parameters - retries - retries.id - retries.isEnabledForRecovery - retries.success
- [View recoveries](https://docs.nexiopay.com/reference/viewrecoverystatus-1.md): Returns declined transactions within the given date range along with the [decline recovery](doc:constant-transaction-values#recovery-status-recoverystatus) status of each. For additional information about this endpoint, see the [Retrieving transaction list from decline recovery](doc:retrieving-transaction-list-from-decline-recovery) tutorial. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - endDate - limit - offset - startDate - recoveryStatus ## Response parameters - offset - limit - rows - rows.id - rows.retryDate - rows.transactionDate - rows.originalAmount - rows.originalDeclinePaymentId - rows.orderNumber - rows.recoveryStatus - rows.retryCount - rows.merchantId - rows.userName - rows.isEnabledForRecovery - rows.declineMessage - rows.updatedAt - hasMore
- [View a recovery](https://docs.nexiopay.com/reference/viewrecovery-1.md): Returns a single decline recovery transaction. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include the retry ID in the path parameter of the request. ## Request parameters - retryId ## Response parameters - id - cardToken - retryDate - transactionDate - originalAmount - originalDeclinePaymentId - retryEngineType - retryProviderRefNumber - orderNumber - recoveryStatus - retryCount - merchantId - originalPaymentRequest - retryMetadata - userName - isEnabledForRecovery - retryProviderBody - declineMessage - createdAt - updatedAt
- [Enable or disable retries for a single transaction](https://docs.nexiopay.com/reference/enableordisableretriesforasingletransaction-1.md): Allows the merchant to enable or disable retries for a single transaction when that transaction is declined. For more information, see the [Decline recovery overview](doc:decline-recovery-overview). > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include at least the retry ID in the body of the request. ## Request parameters - id - isEnabledForRecovery ## Response parameters - id - isEnabledForRecovery - success
- [Enable or disable retries for multiple transactions](https://docs.nexiopay.com/reference/enableordisableretriesformultipletransactions-1.md): Allows the merchant to enable or disable retries for multiple transactions when those transactions are declined. For more information, see the [Decline recovery overview](doc:decline-recovery-overview). > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include at minumum one or more retry IDs in an array in the body of the request. ## Request parameters - retries - retries.id - retries.isEnabledForRecovery ## Response parameters - retries - retries.id - retries.isEnabledForRecovery - retries.success
- [View a chargeback](https://docs.nexiopay.com/reference/viewchargeback.md): Returns a single chargeback record. If you don't know the chargeback ID, use the [View chargebacks](ref:viewchargebacks) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include the chargeback ID as a path parameter for the request. ## Request parameters - id ## Response parameters - id - relatedChargebackId - merchantId - reportDate - sequenceNumber - cardType - cardNumber - amount - transactionDate - reasonCode - description - referenceNumber - message - authCode - lockBoxBatch - cardIdentifier - transactionCode - transactionId - transactionRef - chargebackCycle - isDisputed - achId - achDetailsId - currencyId - createdAt - updatedAt - disputes - disputes.id - disputes.merchantId - disputes.chargebackId - disputes.createdAt - disputes.updatedAt - processor - processor.id - processor.originalId - processor.processorType - processor.originalTransactionId - processor.chargebackId - transaction - transaction.chargebackId - transaction.transactionId - transaction.orderNumber - transaction.cardHolder - transaction.transactionDate - transaction.amount - reason - reason.name - reason.description
- [View chargebacks](https://docs.nexiopay.com/reference/viewchargebacks.md): Returns all chargebacks within the given date range for all merchant IDs associated with the Nexio account used to [authenticate](doc:authentication). You may also request or filter on fields of the query parameters, as in the following example: /chargeback/v3?kount.&plugin.&customer.&processor.&gateway. See the [query parameters](doc:filtering-using-query-parameters) section in Guides for a full tutorial. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - endDate - limit - offset - startDate ## Response parameters - offset - limit - rows - rows.id - rows.relatedChargebackId - rows.merchantId - rows.reportDate - rows.sequenceNumber - rows.cardType - rows.cardNumber - rows.amount - rows.transactionDate - rows.reasonCode - rows.description - rows.referenceNumber - rows.message - rows.authCode - rows.lockBoxBatch - rows.cardIdentifier - rows.transactionCode - rows.transactionId - rows.transactionRef - rows.chargebackCycle - rows.isDisputed - rows.achId - rows.achDetailsId - rows.currencyId - rows.emailSentDate - rows.createdAt - rows.updatedAt - hasMore
- [View chargeback summary](https://docs.nexiopay.com/reference/viewchargebacksummary.md): Returns a summary of all chargebacks within the default or specified date range. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - endDate - startDate ## Response parameters - newChargebacksCount - newChargebacksTotal - wonChargebacksCount - wonChargebacksTotal - representmentsCount - representmentsTotal
- [View a dispute](https://docs.nexiopay.com/reference/viewdispute.md): Returns information about a disputed chargeback. If you don't know the dispute ID, use the [View disputes](ref:viewdisputes) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include the chargeback ID as a path parameter for the request. ## Request parameters - id ## Response parameters - id - merchantId - chargebackId - createdAt - updatedAt
- [Dispute a chargeback](https://docs.nexiopay.com/reference/disputechargeback.md): Flags a chargeback as disputed. You may include additional information if wanted. > ๐ Note > > By submitting a chargeback dispute via the Nexio API you agree to the following: > "I agree that I am not including sensitive information. Sensitive information includes: full credit or debit card numbers, credit or debit card security codes (CVV/CVC), social security numbers, driver's license numbers, health records, and so forth."
Your dispute will be rejected if you include sensitive information. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include at least the chargeback ID and a Nexio account username. ## Request parameters - chargebackId - userName - description - images - images.name - images.data - isPreview ## Response parameters - message
- [View disputes](https://docs.nexiopay.com/reference/viewdisputes.md): Returns summary information for one or more disputed chargebacks. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - limit - offset ## Response parameters - count - rows - rows.id - rows.merchantId - rows.chargebackId - rows.createdAt - rows.updatedAt - limit
- [View a chargeback](https://docs.nexiopay.com/reference/viewchargeback-1.md): Returns a single chargeback record. If you don't know the chargeback ID, use the [View chargebacks](ref:viewchargebacks) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include the chargeback ID as a path parameter for the request. ## Request parameters - id ## Response parameters - id - relatedChargebackId - merchantId - reportDate - sequenceNumber - cardType - cardNumber - amount - transactionDate - reasonCode - description - referenceNumber - message - authCode - lockBoxBatch - cardIdentifier - transactionCode - transactionId - transactionRef - chargebackCycle - isDisputed - achId - achDetailsId - currencyId - createdAt - updatedAt - disputes - disputes.id - disputes.merchantId - disputes.chargebackId - disputes.createdAt - disputes.updatedAt - processor - processor.id - processor.originalId - processor.processorType - processor.originalTransactionId - processor.chargebackId - transaction - transaction.chargebackId - transaction.transactionId - transaction.orderNumber - transaction.cardHolder - transaction.transactionDate - transaction.amount - reason - reason.name - reason.description
- [View chargebacks](https://docs.nexiopay.com/reference/viewchargebacks-1.md): Returns all chargebacks within the given date range for all merchant IDs associated with the Nexio account used to [authenticate](doc:authentication). You may also request or filter on fields of the query parameters, as in the following example: /chargeback/v3?kount.&plugin.&customer.&processor.&gateway. See the [query parameters](doc:filtering-using-query-parameters) section in Guides for a full tutorial. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - endDate - limit - offset - startDate ## Response parameters - offset - limit - rows - rows.id - rows.relatedChargebackId - rows.merchantId - rows.reportDate - rows.sequenceNumber - rows.cardType - rows.cardNumber - rows.amount - rows.transactionDate - rows.reasonCode - rows.description - rows.referenceNumber - rows.message - rows.authCode - rows.lockBoxBatch - rows.cardIdentifier - rows.transactionCode - rows.transactionId - rows.transactionRef - rows.chargebackCycle - rows.isDisputed - rows.achId - rows.achDetailsId - rows.currencyId - rows.emailSentDate - rows.createdAt - rows.updatedAt - hasMore
- [View chargeback summary](https://docs.nexiopay.com/reference/viewchargebacksummary-1.md): Returns a summary of all chargebacks within the default or specified date range. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - endDate - startDate ## Response parameters - newChargebacksCount - newChargebacksTotal - wonChargebacksCount - wonChargebacksTotal - representmentsCount - representmentsTotal
- [View a dispute](https://docs.nexiopay.com/reference/viewdispute-1.md): Returns information about a disputed chargeback. If you don't know the dispute ID, use the [View disputes](ref:viewdisputes) endpoint. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include the chargeback ID as a path parameter for the request. ## Request parameters - id ## Response parameters - id - merchantId - chargebackId - createdAt - updatedAt
- [Dispute a chargeback](https://docs.nexiopay.com/reference/disputechargeback-1.md): Flags a chargeback as disputed. You may include additional information if wanted. > ๐ Note > > By submitting a chargeback dispute via the Nexio API you agree to the following: > "I agree that I am not including sensitive information. Sensitive information includes: full credit or debit card numbers, credit or debit card security codes (CVV/CVC), social security numbers, driver's license numbers, health records, and so forth."
Your dispute will be rejected if you include sensitive information. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
Include at least the chargeback ID and a Nexio account username. ## Request parameters - chargebackId - userName - description - images - images.name - images.data - isPreview ## Response parameters - message
- [View disputes](https://docs.nexiopay.com/reference/viewdisputes-1.md): Returns summary information for one or more disputed chargebacks. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - limit - offset ## Response parameters - count - rows - rows.id - rows.merchantId - rows.chargebackId - rows.createdAt - rows.updatedAt - limit
- [View deposit summary](https://docs.nexiopay.com/reference/viewdepositsummary.md): Returns a summary of all deposits with the given range for the specified merchant ID or IDs, or for all merchant accounts associated with the API user.
You send the request with zero of more of the query parameters to limit the results as in the following example:
/ach/v3?limit=25&offest=0&startDate=2024-02-01&endDate=2024-02-08&merchantids=000999
See the [Filtering using query parameters](doc:filtering-using-query-parameters) topic in Guides for a full tutorial. Note that if you do not include a parameter for this endpoint, the system uses the default value for the request.
For the response, the amounts presented may be different than what was authorized, as the funds may not have settled yet. Amounts being processed may differ temporarily from batch totals if they experience a temporary risk hold; common reasons include large single transactions, unusual activity, or unexpected volume increases. Check the batch details in a few days after it's finalized.
> โ ๏ธ Try It
>
> To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
## Request parameters
- limit
- offset
- startDate
- endDate
- merchantIds
## Response parameters
- offset
- limit
- rows (array)
- rows.id
- rows.merchantId
- rows.date
- rows.dda
- rows.amount
- rows.currencyId
- rows.createdAt
- rows.updatedAt
- rows.processor
- rows.processor.id
- rows.processor.originalId
- rows.processor.processorType
- rows.details (array)
- rows.details.achDetailId
- rows.details.type
- rows.details.thirdPartyFundedAmount
- rows.details.amount
- rows.details.currencyId
- rows.details.achSummaryId
- rows.details.processor
- rows.details.processor.id
- rows.details.processor.originalId
- rows.details.processor.processorType
- rows.details.processor.batchRef
- rows.details.processor.achDetailId
- hasMore
- [View deposit summary](https://docs.nexiopay.com/reference/viewdepositsummary-1.md): Returns a summary of all deposits with the given range for the specified merchant ID or IDs, or for all merchant accounts associated with the API user.
You send the request with zero of more of the query parameters to limit the results as in the following example:
/ach/v3?limit=25&offest=0&startDate=2024-02-01&endDate=2024-02-08&merchantids=000999
See the [Filtering using query parameters](doc:filtering-using-query-parameters) topic in Guides for a full tutorial. Note that if you do not include a parameter for this endpoint, the system uses the default value for the request.
For the response, the amounts presented may be different than what was authorized, as the funds may not have settled yet. Amounts being processed may differ temporarily from batch totals if they experience a temporary risk hold; common reasons include large single transactions, unusual activity, or unexpected volume increases. Check the batch details in a few days after it's finalized.
> โ ๏ธ Try It
>
> To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments).
## Request parameters
- limit
- offset
- startDate
- endDate
- merchantIds
## Response parameters
- offset
- limit
- rows (array)
- rows.id
- rows.merchantId
- rows.date
- rows.dda
- rows.amount
- rows.currencyId
- rows.createdAt
- rows.updatedAt
- rows.processor
- rows.processor.id
- rows.processor.originalId
- rows.processor.processorType
- rows.details (array)
- rows.details.achDetailId
- rows.details.type
- rows.details.thirdPartyFundedAmount
- rows.details.amount
- rows.details.currencyId
- rows.details.achSummaryId
- rows.details.processor
- rows.details.processor.id
- rows.details.processor.originalId
- rows.details.processor.processorType
- rows.details.processor.batchRef
- rows.details.processor.achDetailId
- hasMore
- [Who am I](https://docs.nexiopay.com/reference/whoami.md): Returns basic user information for the account used to authenticate the request. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Response parameters - userName - cognitoSub - accountType - enabled - firstName - lastName - phone - address1 - address2 - city - state - postalCode - country - businessLegalName - billingContactFullName - billingContactPhone - billingContactEmail - isApiUser - isEnabledForCybersourceAccountUpdater - isEnabledForAccountUpdater - accessRights - accessRights.merchantIds - accessRights.role - payoutAccessRights - loginInfo - loginInfo.count - loginInfo.lastLogin - notifications - notifications.chargebacks - notifications.largeExports - notifications.fraud - notifications.payoutBatches - role - isEnabledAuthorizedStatus - isEnabledForVTerm - accountId - shouldShowPlatformAgreement - shouldShowPricingAgreement - dateCreated - dateLastModified
- [Update self](https://docs.nexiopay.com/reference/updateself.md): Updates user information. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - firstName - lastName - phone - notifications ## Response parameters - userName - firstName - lastName - phone - enabled - notifications - accessRights - accessRights.merchantIds - accessRights.role - accountId - role - customAccess - cognitoSub - isEnabledForVTerm - shouldShowPlatformAgreement - shouldShowPricingAgreement - dateCreated - dateLastModified
- [Create user](https://docs.nexiopay.com/reference/createuser.md): Creates a new user. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). > > Include at least the email address and value for the role of this new user. ## Request parameters - email - role -merchantIds ## Response parameters - message
- [Refresh credentials](https://docs.nexiopay.com/reference/refreshcredentials.md): Refreshes your credentials. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). > > Include the `refreshToken` from the [View credentials](ref:viewcredentials) endpoint. ## Request parameters - refreshToken ## Response parameters - idToken - accessToken - refreshToken - expiresIn
- [View credentials](https://docs.nexiopay.com/reference/viewcredentials.md): Retrieves authentication credentials based on username and password. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - username - password ## Response parameters - idToken - accessToken - refreshToken - expiresIn
- [Who am I](https://docs.nexiopay.com/reference/whoami-1.md): Returns basic user information for the account used to authenticate the request. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Response parameters - userName - cognitoSub - accountType - enabled - firstName - lastName - phone - address1 - address2 - city - state - postalCode - country - businessLegalName - billingContactFullName - billingContactPhone - billingContactEmail - isApiUser - isEnabledForCybersourceAccountUpdater - isEnabledForAccountUpdater - accessRights - accessRights.merchantIds - accessRights.role - payoutAccessRights - loginInfo - loginInfo.count - loginInfo.lastLogin - notifications - notifications.chargebacks - notifications.largeExports - notifications.fraud - notifications.payoutBatches - role - isEnabledAuthorizedStatus - isEnabledForVTerm - accountId - shouldShowPlatformAgreement - shouldShowPricingAgreement - dateCreated - dateLastModified
- [Update self](https://docs.nexiopay.com/reference/updateself-1.md): Updates user information. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - firstName - lastName - phone - notifications ## Response parameters - userName - firstName - lastName - phone - enabled - notifications - accessRights - accessRights.merchantIds - accessRights.role - accountId - role - customAccess - cognitoSub - isEnabledForVTerm - shouldShowPlatformAgreement - shouldShowPricingAgreement - dateCreated - dateLastModified
- [Create user](https://docs.nexiopay.com/reference/createuser-1.md): Creates a new user. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). > > Include at least the email address and value for the role of this new user. ## Request parameters - email - role -merchantIds ## Response parameters - message
- [Refresh credentials](https://docs.nexiopay.com/reference/refreshcredentials-1.md): Refreshes your credentials. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). > > Include the `refreshToken` from the [View credentials](ref:viewcredentials) endpoint. ## Request parameters - refreshToken ## Response parameters - idToken - accessToken - refreshToken - expiresIn
- [View credentials](https://docs.nexiopay.com/reference/viewcredentials-1.md): Retrieves authentication credentials based on username and password. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - username - password ## Response parameters - idToken - accessToken - refreshToken - expiresIn
- [View merchants by ID](https://docs.nexiopay.com/reference/viewmerchantsid.md): Returns an array with information for one or more merchant accounts associated with the API user. To view the complete list of merchant accounts assigned to the API user, do not include any merchant IDs in the request. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - merchantIds ## Response parameters - merchantId - name - currencyId - isPaymentConfigured - isPaymentRecoveryConfigured - processor - processor.id - kountMerc - kount - kount.id - kount.merc - kount.merchantId - isApmConfigured - hasAuthorizeNetApmCreds - createdAt - updatedAt
- [View merchants by ID](https://docs.nexiopay.com/reference/viewmerchantsid-1.md): Returns an array with information for one or more merchant accounts associated with the API user. To view the complete list of merchant accounts assigned to the API user, do not include any merchant IDs in the request. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - merchantIds ## Response parameters - merchantId - name - currencyId - isPaymentConfigured - isPaymentRecoveryConfigured - processor - processor.id - kountMerc - kount - kount.id - kount.merc - kount.merchantId - isApmConfigured - hasAuthorizeNetApmCreds - createdAt - updatedAt
- [Register webhook URLs](https://docs.nexiopay.com/reference/registerwebhookurls.md): **New webhook workflow** Registers webhooks for a specific merchant ID or payout account ID. These webhooks are callbacks for transactions, payouts, or spendbacks. - Each webhook for a merchant ID receives the same information for all transaction events. - Each webhook for a payout account ID receives the same information for all payout and spendback events. You can create multiple webhooks for the same merchant ID or payout account ID. This is useful for situations where you have multiple workflows from a single event, such as when you need to send the information to two different internal departments but they need to do different things with the same information. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). > ๐ Important > > Nexio supports only either the legacy webhooks or these new ones. Before configuring URLs for your webhooks, ensure that you do not have any URLs for legacy ones configured: [View legacy merchant webhook configuration](ref:viewmerchantwebhookconfiguration). ## Request parameters - merchantId - webhookUrls - payoutAccountId - accountId ## Response parameters - merchantId - payoutAccountId - accountId - webhookUrls - dateCreated - dateLastModified
## Next steps * If needed, whitelist the IP addresses that send the webhooks. You can find the list for both sandbox and production environments at [https://ip-ranges.nex.io/ip-ranges.json](https://ip-ranges.nex.io/ip-ranges.json). * [Retrieve a list of webhook URLs](ref:viewwebhookurlsbyidandtype) that are registered for a merchant ID or payout account ID. * For a tutorial on how to register and use webhooks, see [Webhooks](doc:webhooks) in Guides. For the legacy method for creating webhooks, see the [Create legacy merchant webhooks](ref:createmerchantwebhooks) endpoint.
- [View webhook URLs by ID and type](https://docs.nexiopay.com/reference/viewwebhookurlsbyidandtype.md): **Simplified webhook workflow** Returns the registered webhook URLs for the specified ID and webhook type. The ID can be either a merchant ID, payout account ID, or reseller Nexio account ID. The webhook type needs to match the ID. For a tutorial on how to register and use webhooks, see [Webhooks](doc:webhooks) in Guides. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - id - webhook_type ## Response parameters - merchantId - payoutAccountId - accountId - webhookUrls - dateCreated - dateLastModified
- [Create legacy merchant webhooks](https://docs.nexiopay.com/reference/createmerchantwebhooks.md): Configures webhooks using the legacy workflow, including the URLs a merchant's webhooks are sent to and the event types which trigger webhooks. If you need to whitelist the IP addresses that send the webhooks, you can find the list for both sandbox and production environments at [https://ip-ranges.nex.io/ip-ranges.json](https://ip-ranges.nex.io/ip-ranges.json). For a tutorial about configuring and using webhooks, see [Configuring webhooks](doc:configuring-legacy-webhooks) in Guides. > ๐ Note > > For the current workflow, see the [Register webhook URLs](ref:registerwebhookurls) endpoint instead. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). > ๐ Important > > Nexio supports only either the new webhooks or these legacy ones. Before configuring URLs for legacy webhooks, ensure that you do not have any URLS for the new ones configured: [View webhook URLs by ID and type](ref:viewwebhookurlsbyidandtype). > > If you need to remove one or more (or all) legacy webhooks, use this endpoint, but send an empty `webhooks` object to remove all or, to remove just one, send all current configured webhooks minus the object that corresponds to the event type for the webhook you want to remove. For additional information, see [Deregistering legacy webhooks](doc:) in Guides. ## Request parameters - merchantId - payoutAccountId - webhooks - webhooks.ACCOUNT_UPDATER_ACCOUNT_CLOSED - webhooks.ACCOUNT_UPDATER_ACCOUNT_CLOSED.url - webhooks.ACCOUNT_UPDATER_CONTACT_CARDHOLDER - webhooks.ACCOUNT_UPDATER_CONTACT_CARDHOLDER.url - webhooks.CARD_DATA_UPDATED - webhooks.CARD_DATA_UPDATED.url - webhooks.CARD_SAVED - webhooks.CARD_SAVED.url - webhooks.ECHECK_SAVED - webhooks.ECHECK_SAVED.url - webhooks.SUBSCRIPTION_DETAILS - webhooks.SUBSCRIPTION_DETAILS.url - webhooks.TRANSACTION_AUTHORIZED - webhooks.TRANSACTION_AUTHORIZED.url - webhooks.TRANSACTION_CAPTURED - webhooks.TRANSACTION_CAPTURED.url - webhooks.TRANSACTION_PENDING - webhooks.TRANSACTION_PENDING.url - webhooks.TRANSACTION_REFUNDED - webhooks.TRANSACTION_REFUNDED.url - webhooks.TRANSACTION_SETTLED - webhooks.TRANSACTION_SETTLED.url - webhooks.TRANSACTION_VOIDED - webhooks.TRANSACTION_VOIDED.url - webhooks.PAYOUT - webhooks.PAYOUT.url - webhooks.SPENDBACK - webhooks.SPENDBACK.url ## Response parameters - merchantId - payoutAccountId - webhooks - webhooks.ACCOUNT_UPDATER_ACCOUNT_CLOSED - webhooks.ACCOUNT_UPDATER_ACCOUNT_CLOSED.url - webhooks.ACCOUNT_UPDATER_CONTACT_CARDHOLDER - webhooks.ACCOUNT_UPDATER_CONTACT_CARDHOLDER.url - webhooks.CARD_DATA_UPDATED - webhooks.CARD_DATA_UPDATED.url - webhooks.CARD_SAVED - webhooks.CARD_SAVED.url - webhooks.ECHECK_SAVED - webhooks.ECHECK_SAVED.url - webhooks.SUBSCRIPTION_DETAILS - webhooks.SUBSCRIPTION_DETAILS.url - webhooks.TRANSACTION_AUTHORIZED - webhooks.TRANSACTION_AUTHORIZED.url - webhooks.TRANSACTION_CAPTURED - webhooks.TRANSACTION_CAPTURED.url - webhooks.TRANSACTION_PENDING - webhooks.TRANSACTION_PENDING.url - webhooks.TRANSACTION_REFUNDED - webhooks.TRANSACTION_REFUNDED.url - webhooks.TRANSACTION_SETTLED - webhooks.TRANSACTION_SETTLED.url - webhooks.TRANSACTION_VOIDED - webhooks.TRANSACTION_VOIDED.url - webhooks.PAYOUT - webhooks.PAYOUT.url - webhooks.SPENDBACK - webhooks.SPENDBACK.url - dateCreated - dateLastModified
- [View legacy merchant webhook configuration](https://docs.nexiopay.com/reference/viewmerchantwebhookconfiguration.md): Returns a merchant's webhook configuration. For a tutorial about configuring and using webhooks, see [Configuring legacy webhooks](doc:configuring-legacy-webhooks) in Guides. > ๐ Note > > For the current workflow, see the [View webhook URLs by ID and type](ref:viewwebhookurlsbyidandtype) endpoint instead. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - id ## Response parameters - merchantId - payoutAccountId - webhooks - webhooks.ACCOUNT_UPDATER_ACCOUNT_CLOSED - webhooks.ACCOUNT_UPDATER_ACCOUNT_CLOSED.url - webhooks.ACCOUNT_UPDATER_CONTACT_CARDHOLDER - webhooks.ACCOUNT_UPDATER_CONTACT_CARDHOLDER.url - webhooks.CARD_DATA_UPDATED - webhooks.CARD_DATA_UPDATED.url - webhooks.CARD_SAVED - webhooks.CARD_SAVED.url - webhooks.ECHECK_SAVED - webhooks.ECHECK_SAVED.url - webhooks.SUBSCRIPTION_DETAILS - webhooks.SUBSCRIPTION_DETAILS.url - webhooks.TRANSACTION_AUTHORIZED - webhooks.TRANSACTION_AUTHORIZED.url - webhooks.TRANSACTION_CAPTURED - webhooks.TRANSACTION_CAPTURED.url - webhooks.TRANSACTION_PENDING - webhooks.TRANSACTION_PENDING.url - webhooks.TRANSACTION_REFUNDED - webhooks.TRANSACTION_REFUNDED.url - webhooks.TRANSACTION_SETTLED - webhooks.TRANSACTION_SETTLED.url - webhooks.TRANSACTION_VOIDED - webhooks.TRANSACTION_VOIDED.url - webhooks.PAYOUT - webhooks.PAYOUT.url - webhooks.SPENDBACK - webhooks.SPENDBACK.url - dateCreated - dateLastModified
- [Create a webhook secret](https://docs.nexiopay.com/reference/createwebhooksecret.md): Creates a secret to be used in legacy webhooks for a merchant account or payout account. Set up a webhook secret for additional security. After you create a secret, each webhook includes a header containing a signature. You can use the signature to verify that all data received is authentic. For a tutorial about configuring and using webhooks, see [Configuring legacy webhooks](doc:configuring-legacy-webhooks) in Guides. > ๐ Note > > For the current workflow, see the [Register webhook URLs](ref:registerwebhookurls) endpoint instead. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - merchantId - payoutAccountId ## Response parameters - secret
- [View webhook secret](https://docs.nexiopay.com/reference/viewwebhooksecret.md): Returns the webhook secret to be used in validating legacy webhooks for the specified merchant ID or payout account ID. To create a secret, use the [/webhook/v3/secret](ref:createwebhooksecret) endpoint. For a tutorial about verifying the signature, see [Receiving legacy webhooks](doc:receiving-legacy-webhooks) in Guides. > ๐ Note > > For the current workflow, see the [Register webhook URLs](ref:registerwebhookurls) endpoint instead. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - id ## Response parameters - secret
- [Register webhook URLs](https://docs.nexiopay.com/reference/registerwebhookurls-1.md): **New webhook workflow** Registers webhooks for a specific merchant ID or payout account ID. These webhooks are callbacks for transactions, payouts, or spendbacks. - Each webhook for a merchant ID receives the same information for all transaction events. - Each webhook for a payout account ID receives the same information for all payout and spendback events. You can create multiple webhooks for the same merchant ID or payout account ID. This is useful for situations where you have multiple workflows from a single event, such as when you need to send the information to two different internal departments but they need to do different things with the same information. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). > ๐ Important > > Nexio supports only either the legacy webhooks or these new ones. Before configuring URLs for your webhooks, ensure that you do not have any URLs for legacy ones configured: [View legacy merchant webhook configuration](ref:viewmerchantwebhookconfiguration). ## Request parameters - merchantId - webhookUrls - payoutAccountId - accountId ## Response parameters - merchantId - payoutAccountId - accountId - webhookUrls - dateCreated - dateLastModified
## Next steps * If needed, whitelist the IP addresses that send the webhooks. You can find the list for both sandbox and production environments at [https://ip-ranges.nex.io/ip-ranges.json](https://ip-ranges.nex.io/ip-ranges.json). * [Retrieve a list of webhook URLs](ref:viewwebhookurlsbyidandtype) that are registered for a merchant ID or payout account ID. * For a tutorial on how to register and use webhooks, see [Webhooks](doc:webhooks) in Guides. For the legacy method for creating webhooks, see the [Create legacy merchant webhooks](ref:createmerchantwebhooks) endpoint.
- [View webhook URLs by ID and type](https://docs.nexiopay.com/reference/viewwebhookurlsbyidandtype-1.md): **Simplified webhook workflow** Returns the registered webhook URLs for the specified ID and webhook type. The ID can be either a merchant ID, payout account ID, or reseller Nexio account ID. The webhook type needs to match the ID. For a tutorial on how to register and use webhooks, see [Webhooks](doc:webhooks) in Guides. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - id - webhook_type ## Response parameters - merchantId - payoutAccountId - accountId - webhookUrls - dateCreated - dateLastModified
- [Create legacy merchant webhooks](https://docs.nexiopay.com/reference/createmerchantwebhooks-1.md): Configures webhooks using the legacy workflow, including the URLs a merchant's webhooks are sent to and the event types which trigger webhooks. If you need to whitelist the IP addresses that send the webhooks, you can find the list for both sandbox and production environments at [https://ip-ranges.nex.io/ip-ranges.json](https://ip-ranges.nex.io/ip-ranges.json). For a tutorial about configuring and using webhooks, see [Configuring webhooks](doc:configuring-legacy-webhooks) in Guides. > ๐ Note > > For the current workflow, see the [Register webhook URLs](ref:registerwebhookurls) endpoint instead. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). > ๐ Important > > Nexio supports only either the new webhooks or these legacy ones. Before configuring URLs for legacy webhooks, ensure that you do not have any URLS for the new ones configured: [View webhook URLs by ID and type](ref:viewwebhookurlsbyidandtype). > > If you need to remove one or more (or all) legacy webhooks, use this endpoint, but send an empty `webhooks` object to remove all or, to remove just one, send all current configured webhooks minus the object that corresponds to the event type for the webhook you want to remove. For additional information, see [Deregistering legacy webhooks](doc:) in Guides. ## Request parameters - merchantId - payoutAccountId - webhooks - webhooks.ACCOUNT_UPDATER_ACCOUNT_CLOSED - webhooks.ACCOUNT_UPDATER_ACCOUNT_CLOSED.url - webhooks.ACCOUNT_UPDATER_CONTACT_CARDHOLDER - webhooks.ACCOUNT_UPDATER_CONTACT_CARDHOLDER.url - webhooks.CARD_DATA_UPDATED - webhooks.CARD_DATA_UPDATED.url - webhooks.CARD_SAVED - webhooks.CARD_SAVED.url - webhooks.ECHECK_SAVED - webhooks.ECHECK_SAVED.url - webhooks.SUBSCRIPTION_DETAILS - webhooks.SUBSCRIPTION_DETAILS.url - webhooks.TRANSACTION_AUTHORIZED - webhooks.TRANSACTION_AUTHORIZED.url - webhooks.TRANSACTION_CAPTURED - webhooks.TRANSACTION_CAPTURED.url - webhooks.TRANSACTION_PENDING - webhooks.TRANSACTION_PENDING.url - webhooks.TRANSACTION_REFUNDED - webhooks.TRANSACTION_REFUNDED.url - webhooks.TRANSACTION_SETTLED - webhooks.TRANSACTION_SETTLED.url - webhooks.TRANSACTION_VOIDED - webhooks.TRANSACTION_VOIDED.url - webhooks.PAYOUT - webhooks.PAYOUT.url - webhooks.SPENDBACK - webhooks.SPENDBACK.url ## Response parameters - merchantId - payoutAccountId - webhooks - webhooks.ACCOUNT_UPDATER_ACCOUNT_CLOSED - webhooks.ACCOUNT_UPDATER_ACCOUNT_CLOSED.url - webhooks.ACCOUNT_UPDATER_CONTACT_CARDHOLDER - webhooks.ACCOUNT_UPDATER_CONTACT_CARDHOLDER.url - webhooks.CARD_DATA_UPDATED - webhooks.CARD_DATA_UPDATED.url - webhooks.CARD_SAVED - webhooks.CARD_SAVED.url - webhooks.ECHECK_SAVED - webhooks.ECHECK_SAVED.url - webhooks.SUBSCRIPTION_DETAILS - webhooks.SUBSCRIPTION_DETAILS.url - webhooks.TRANSACTION_AUTHORIZED - webhooks.TRANSACTION_AUTHORIZED.url - webhooks.TRANSACTION_CAPTURED - webhooks.TRANSACTION_CAPTURED.url - webhooks.TRANSACTION_PENDING - webhooks.TRANSACTION_PENDING.url - webhooks.TRANSACTION_REFUNDED - webhooks.TRANSACTION_REFUNDED.url - webhooks.TRANSACTION_SETTLED - webhooks.TRANSACTION_SETTLED.url - webhooks.TRANSACTION_VOIDED - webhooks.TRANSACTION_VOIDED.url - webhooks.PAYOUT - webhooks.PAYOUT.url - webhooks.SPENDBACK - webhooks.SPENDBACK.url - dateCreated - dateLastModified
- [View legacy merchant webhook configuration](https://docs.nexiopay.com/reference/viewmerchantwebhookconfiguration-1.md): Returns a merchant's webhook configuration. For a tutorial about configuring and using webhooks, see [Configuring legacy webhooks](doc:configuring-legacy-webhooks) in Guides. > ๐ Note > > For the current workflow, see the [View webhook URLs by ID and type](ref:viewwebhookurlsbyidandtype) endpoint instead. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - id ## Response parameters - merchantId - payoutAccountId - webhooks - webhooks.ACCOUNT_UPDATER_ACCOUNT_CLOSED - webhooks.ACCOUNT_UPDATER_ACCOUNT_CLOSED.url - webhooks.ACCOUNT_UPDATER_CONTACT_CARDHOLDER - webhooks.ACCOUNT_UPDATER_CONTACT_CARDHOLDER.url - webhooks.CARD_DATA_UPDATED - webhooks.CARD_DATA_UPDATED.url - webhooks.CARD_SAVED - webhooks.CARD_SAVED.url - webhooks.ECHECK_SAVED - webhooks.ECHECK_SAVED.url - webhooks.SUBSCRIPTION_DETAILS - webhooks.SUBSCRIPTION_DETAILS.url - webhooks.TRANSACTION_AUTHORIZED - webhooks.TRANSACTION_AUTHORIZED.url - webhooks.TRANSACTION_CAPTURED - webhooks.TRANSACTION_CAPTURED.url - webhooks.TRANSACTION_PENDING - webhooks.TRANSACTION_PENDING.url - webhooks.TRANSACTION_REFUNDED - webhooks.TRANSACTION_REFUNDED.url - webhooks.TRANSACTION_SETTLED - webhooks.TRANSACTION_SETTLED.url - webhooks.TRANSACTION_VOIDED - webhooks.TRANSACTION_VOIDED.url - webhooks.PAYOUT - webhooks.PAYOUT.url - webhooks.SPENDBACK - webhooks.SPENDBACK.url - dateCreated - dateLastModified
- [Create a webhook secret](https://docs.nexiopay.com/reference/createwebhooksecret-1.md): Creates a secret to be used in legacy webhooks for a merchant account or payout account. Set up a webhook secret for additional security. After you create a secret, each webhook includes a header containing a signature. You can use the signature to verify that all data received is authentic. For a tutorial about configuring and using webhooks, see [Configuring legacy webhooks](doc:configuring-legacy-webhooks) in Guides. > ๐ Note > > For the current workflow, see the [Register webhook URLs](ref:registerwebhookurls) endpoint instead. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - merchantId - payoutAccountId ## Response parameters - secret
- [View webhook secret](https://docs.nexiopay.com/reference/viewwebhooksecret-1.md): Returns the webhook secret to be used in validating legacy webhooks for the specified merchant ID or payout account ID. To create a secret, use the [/webhook/v3/secret](ref:createwebhooksecret) endpoint. For a tutorial about verifying the signature, see [Receiving legacy webhooks](doc:receiving-legacy-webhooks) in Guides. > ๐ Note > > For the current workflow, see the [Register webhook URLs](ref:registerwebhookurls) endpoint instead. > โ ๏ธ Try It > > To use the Try It feature for this endpoint, you must use the credentials for your [Sandbox API user](doc:sandbox-environments). ## Request parameters - id ## Response parameters - secret
- [Create online application](https://docs.nexiopay.com/reference/onlineapplication.md): Creates a prefilled form for the online application. The 'pricing' object is optional. However, if included in the request, include all required and any applicable conditionally required parameters. > ๐ Notes > > - You cannot use this endpoint in the Nexio sandbox environment. > - For authentication with this endpoint, use your CForce credentials. > โ ๏ธ Try It > > Due to technical limitations, it is not possible to use the **Try It** feature with this endpoint. Instead, use something like Postman or your own server to make the request with the [base URL for the Nexio production environment](doc:base-urls-and-environments). ## Request parameters - partner - partner.applicationType - partner.repCode - partner.checkCredit - partner.hasPersonalGuarantor - partner.repName - partner.contact - partner.agentEmail - partner.partnerRef - partner.redirectUrl - partner.sendEmail - partner.sendEmailMessage - owners - owners.owner1 - owners.owner2 - owners.owner3 - owners.owner4 - owners.owner[n].email - owners.owner[n].firstName - owners.owner[n].middleInitial - owners.owner[n].lastName - owners.owner[n].title - owners.owner[n].phone - owners.owner[n].address - owners.owner[n].city - owners.owner[n].state - owners.owner[n].postal - owners.owner[n].country - owners.owner[n].birthday - owners.owner[n].socialSecurityNumber - owners.owner[n].ownershipPercentage - owners.owner[n].identificationType - owners.owner[n].identificationState - owners.owner[n].identificationNumber - business - business.taxPayerId - business.dbaName - business.legalName - business.legalSameAsDBA - business.businessStartDate - business.businessType - business.marketType - business.productDescription - business.website - business.businessPhone - business.corporatePhone - business.customerServicePhone - business.fax - business.contactFirstName - business.contactLastName - business.contactEmail - business.businessAddress - business.businessCity - business.businessState - business.businessPostal - business.businessCountry - business.legalAddress - business.legalCity - business.legalState - business.legalPostal - business.legalCountry - merchantProfile - merchantProfile.isDirectSalesMLM - merchantProfile.acceptCard - merchantProfile.acceptPrePayment - merchantProfile.warranty - merchantProfile.averageTicketAmount - merchantProfile.highTicket - merchantProfile.monthlySalesVolume - merchantProfile.amex - merchantProfile.amexSe - merchantProfile.cardPresentSwiped - merchantProfile.cardPresentKeyed - merchantProfile.cardNotPresentMOTO - merchantProfile.cardNotPresentECommerce - bank - bank.routingNumber - bank.accountNumber - compliance - compliance.adc - compliance.adcDate - compliance.pcidss - compliance.pcidssDate - compliance.fcn - compliance.otherServiceProvider - compliance.otherServiceProviderName - pricing - pricing.pricingNotes - pricing.accountSetupFee - pricing.annualMembershipFee - pricing.annualPciComplianceFee - pricing.accountServiceFee - pricing.chargebackFee - pricing.edcAVSFee - pricing.helpDeskFee - pricing.insufficientFundsFee - pricing.monthlyBreachInsuranceFee - pricing.monthlyDebitAccessFee - pricing.monthlyMinimumFee - pricing.monthlyRegulatoryFee - pricing.onlineReportingAccessFee - pricing.retrievalFee - pricing.commercialNonQualifiedRate - pricing.pinDebitPerItem - pricing.pinDebitRate - pricing.amexPricingType - pricing.amexERRQualified - pricing.amexERRNonQualified - pricing.amexInterchange - pricing.amexTieredQualified - pricing.amexTieredMidQualified - pricing.amexTieredNonQualified - pricing.visaAuth - pricing.visaBatch - pricing.visaPricingType - pricing.visaERRQualified - pricing.visaERRNonQualified - pricing.visaInterchange - pricing.visaTieredQualified - pricing.visaTieredMidQualified - pricing.visaTieredNonQualified - directSalesMLM - directSalesMLM.generalProductsServices - directSalesMLM.generalAdvertise - directSalesMLM.financialBankruptcy - directSalesMLM.financialCommissionsRecruiting - directSalesMLM.financialCommissionsSales - directSalesMLM.financialGrossRevenue - directSalesMLM.financialRecruitingGrossRevenuePercentage - directSalesMLM.financialStartup - directSalesMLM.operationalAdvanceCharges - directSalesMLM.operationalComplaints - directSalesMLM.operationalDistributorContract - directSalesMLM.operationalDistributorDoc - directSalesMLM.operationalDoesOfferTrial - directSalesMLM.operationalHasPeakSeason - directSalesMLM.operationalInventoryPurchase - directSalesMLM.operationalMailTelephoneOrders - directSalesMLM.operationalPeakSeason - directSalesMLM.operationalPhysicalLocations - directSalesMLM.operationalProductFulfillment - directSalesMLM.operationalRecurringBilling - directSalesMLM.operationalRecurringBillingInfo - directSalesMLM.operationalRefunds - directSalesMLM.operationalRestockingFees - directSalesMLM.operationalTraining - directSalesMLM.operationalTrialOffer - directSalesMLM.reputationalAttorney - directSalesMLM.reputationalContact - directSalesMLM.reputationalDSA - directSalesMLM.reputationalIndictment - directSalesMLM.reputationalSanctions - directSalesMLM.reputationalShipping - directSalesMLM.reputationalWorkingWithAttorney - merchantSiteSurveyReport - merchantSiteSurveyReport.merchantLocation - merchantSiteSurveyReport.merchantLocationOther - merchantProfileAnalysis - merchantProfileAnalysis.generalUsername - merchantProfileAnalysis.generalPassword - merchantProfileAnalysis.generalControlPerson - merchantProfileAnalysis.questionsContactNumber - merchantProfileAnalysis.generalAdvertise - merchantProfileAnalysis.generalBilledFrequency - merchantProfileAnalysis.generalCancellation - merchantProfileAnalysis.generalCardPayments - merchantProfileAnalysis.generalInAdvance - merchantProfileAnalysis.generalInventory - merchantProfileAnalysis.generalNutraceutical - merchantProfileAnalysis.generalProductsServices - merchantProfileAnalysis.generalRefund - merchantProfileAnalysis.generalTelemarketing - merchantProfileAnalysis.isCollectionServices - merchantProfileAnalysis.collectionDebtType - merchantProfileAnalysis.collectionIndustries - merchantProfileAnalysis.isConsulting - merchantProfileAnalysis.consultingDescribe - merchantProfileAnalysis.consultingFiling - merchantProfileAnalysis.isCreditRepairServices - merchantProfileAnalysis.creditRepairAttorneyStaff - merchantProfileAnalysis.creditRepairFees - merchantProfileAnalysis.creditRepairTelemarketing - merchantProfileAnalysis.isLendingServices - merchantProfileAnalysis.lendingDisclose - merchantProfileAnalysis.lendingOriginate - merchantProfileAnalysis.isTravel - merchantProfileAnalysis.travelARC - merchantProfileAnalysis.travelCompany - merchantProfileAnalysis.travelInsurance - merchantProfileAnalysis.travelLicensedStates - merchantProfileAnalysis.travelThirdParty ## Response parameters - merchantLink - token
- [View application by onboarding ID](https://docs.nexiopay.com/reference/viewapplicationonboardingid.md): Returns the application information for a specific `onboardingId` that is associated with the Nexio account used to [authenticate](doc:authentication). > ๐ Notes > > - You cannot use this endpoint in the sandbox environment. > - For authentication with this endpoint, use your Production API user credentials. > โ ๏ธ Try It > > Due to technical limitations, it is not possible to use the Try It feature with this endpoint. Instead, for the production environment, use something like Postman or your own server (along with the credentials for your [Production API user](doc:sandbox-environments#production-environment)) to make the request. ## Request parameters - onboardingId ## Response parameters - merchantName - merchantId - status - signer - phoneNumber - agentName - repCode - agentId - onboardingId - credsReady - pendingItemsUpdatedAt - pendingNotes.dateAdded - pendingNotes.note - apiUserCredentials.apiKey - apiUserCredentials.userName - apiUserCredentials.merchantIds - apiUserCredentials.accountId
- [Create online application](https://docs.nexiopay.com/reference/onlineapplication-1.md): Creates a prefilled form for the online application. The 'pricing' object is optional. However, if included in the request, include all required and any applicable conditionally required parameters. > ๐ Notes > > - You cannot use this endpoint in the Nexio sandbox environment. > - For authentication with this endpoint, use your CForce credentials. > โ ๏ธ Try It > > Due to technical limitations, it is not possible to use the **Try It** feature with this endpoint. Instead, use something like Postman or your own server to make the request with the [base URL for the Nexio production environment](doc:base-urls-and-environments). ## Request parameters - partner - partner.applicationType - partner.repCode - partner.checkCredit - partner.hasPersonalGuarantor - partner.repName - partner.contact - partner.agentEmail - partner.partnerRef - partner.redirectUrl - partner.sendEmail - partner.sendEmailMessage - owners - owners.owner1 - owners.owner2 - owners.owner3 - owners.owner4 - owners.owner[n].email - owners.owner[n].firstName - owners.owner[n].middleInitial - owners.owner[n].lastName - owners.owner[n].title - owners.owner[n].phone - owners.owner[n].address - owners.owner[n].city - owners.owner[n].state - owners.owner[n].postal - owners.owner[n].country - owners.owner[n].birthday - owners.owner[n].socialSecurityNumber - owners.owner[n].ownershipPercentage - owners.owner[n].identificationType - owners.owner[n].identificationState - owners.owner[n].identificationNumber - business - business.taxPayerId - business.dbaName - business.legalName - business.legalSameAsDBA - business.businessStartDate - business.businessType - business.marketType - business.productDescription - business.website - business.businessPhone - business.corporatePhone - business.customerServicePhone - business.fax - business.contactFirstName - business.contactLastName - business.contactEmail - business.businessAddress - business.businessCity - business.businessState - business.businessPostal - business.businessCountry - business.legalAddress - business.legalCity - business.legalState - business.legalPostal - business.legalCountry - merchantProfile - merchantProfile.isDirectSalesMLM - merchantProfile.acceptCard - merchantProfile.acceptPrePayment - merchantProfile.warranty - merchantProfile.averageTicketAmount - merchantProfile.highTicket - merchantProfile.monthlySalesVolume - merchantProfile.amex - merchantProfile.amexSe - merchantProfile.cardPresentSwiped - merchantProfile.cardPresentKeyed - merchantProfile.cardNotPresentMOTO - merchantProfile.cardNotPresentECommerce - bank - bank.routingNumber - bank.accountNumber - compliance - compliance.adc - compliance.adcDate - compliance.pcidss - compliance.pcidssDate - compliance.fcn - compliance.otherServiceProvider - compliance.otherServiceProviderName - pricing - pricing.pricingNotes - pricing.accountSetupFee - pricing.annualMembershipFee - pricing.annualPciComplianceFee - pricing.accountServiceFee - pricing.chargebackFee - pricing.edcAVSFee - pricing.helpDeskFee - pricing.insufficientFundsFee - pricing.monthlyBreachInsuranceFee - pricing.monthlyDebitAccessFee - pricing.monthlyMinimumFee - pricing.monthlyRegulatoryFee - pricing.onlineReportingAccessFee - pricing.retrievalFee - pricing.commercialNonQualifiedRate - pricing.pinDebitPerItem - pricing.pinDebitRate - pricing.amexPricingType - pricing.amexERRQualified - pricing.amexERRNonQualified - pricing.amexInterchange - pricing.amexTieredQualified - pricing.amexTieredMidQualified - pricing.amexTieredNonQualified - pricing.visaAuth - pricing.visaBatch - pricing.visaPricingType - pricing.visaERRQualified - pricing.visaERRNonQualified - pricing.visaInterchange - pricing.visaTieredQualified - pricing.visaTieredMidQualified - pricing.visaTieredNonQualified - directSalesMLM - directSalesMLM.generalProductsServices - directSalesMLM.generalAdvertise - directSalesMLM.financialBankruptcy - directSalesMLM.financialCommissionsRecruiting - directSalesMLM.financialCommissionsSales - directSalesMLM.financialGrossRevenue - directSalesMLM.financialRecruitingGrossRevenuePercentage - directSalesMLM.financialStartup - directSalesMLM.operationalAdvanceCharges - directSalesMLM.operationalComplaints - directSalesMLM.operationalDistributorContract - directSalesMLM.operationalDistributorDoc - directSalesMLM.operationalDoesOfferTrial - directSalesMLM.operationalHasPeakSeason - directSalesMLM.operationalInventoryPurchase - directSalesMLM.operationalMailTelephoneOrders - directSalesMLM.operationalPeakSeason - directSalesMLM.operationalPhysicalLocations - directSalesMLM.operationalProductFulfillment - directSalesMLM.operationalRecurringBilling - directSalesMLM.operationalRecurringBillingInfo - directSalesMLM.operationalRefunds - directSalesMLM.operationalRestockingFees - directSalesMLM.operationalTraining - directSalesMLM.operationalTrialOffer - directSalesMLM.reputationalAttorney - directSalesMLM.reputationalContact - directSalesMLM.reputationalDSA - directSalesMLM.reputationalIndictment - directSalesMLM.reputationalSanctions - directSalesMLM.reputationalShipping - directSalesMLM.reputationalWorkingWithAttorney - merchantSiteSurveyReport - merchantSiteSurveyReport.merchantLocation - merchantSiteSurveyReport.merchantLocationOther - merchantProfileAnalysis - merchantProfileAnalysis.generalUsername - merchantProfileAnalysis.generalPassword - merchantProfileAnalysis.generalControlPerson - merchantProfileAnalysis.questionsContactNumber - merchantProfileAnalysis.generalAdvertise - merchantProfileAnalysis.generalBilledFrequency - merchantProfileAnalysis.generalCancellation - merchantProfileAnalysis.generalCardPayments - merchantProfileAnalysis.generalInAdvance - merchantProfileAnalysis.generalInventory - merchantProfileAnalysis.generalNutraceutical - merchantProfileAnalysis.generalProductsServices - merchantProfileAnalysis.generalRefund - merchantProfileAnalysis.generalTelemarketing - merchantProfileAnalysis.isCollectionServices - merchantProfileAnalysis.collectionDebtType - merchantProfileAnalysis.collectionIndustries - merchantProfileAnalysis.isConsulting - merchantProfileAnalysis.consultingDescribe - merchantProfileAnalysis.consultingFiling - merchantProfileAnalysis.isCreditRepairServices - merchantProfileAnalysis.creditRepairAttorneyStaff - merchantProfileAnalysis.creditRepairFees - merchantProfileAnalysis.creditRepairTelemarketing - merchantProfileAnalysis.isLendingServices - merchantProfileAnalysis.lendingDisclose - merchantProfileAnalysis.lendingOriginate - merchantProfileAnalysis.isTravel - merchantProfileAnalysis.travelARC - merchantProfileAnalysis.travelCompany - merchantProfileAnalysis.travelInsurance - merchantProfileAnalysis.travelLicensedStates - merchantProfileAnalysis.travelThirdParty ## Response parameters - merchantLink - token
- [View application by onboarding ID](https://docs.nexiopay.com/reference/viewapplicationonboardingid-1.md): Returns the application information for a specific `onboardingId` that is associated with the Nexio account used to [authenticate](doc:authentication). > ๐ Notes > > - You cannot use this endpoint in the sandbox environment. > - For authentication with this endpoint, use your Production API user credentials. > โ ๏ธ Try It > > Due to technical limitations, it is not possible to use the Try It feature with this endpoint. Instead, for the production environment, use something like Postman or your own server (along with the credentials for your [Production API user](doc:sandbox-environments#production-environment)) to make the request. ## Request parameters - onboardingId ## Response parameters - merchantName - merchantId - status - signer - phoneNumber - agentName - repCode - agentId - onboardingId - credsReady - pendingItemsUpdatedAt - pendingNotes.dateAdded - pendingNotes.note - apiUserCredentials.apiKey - apiUserCredentials.userName - apiUserCredentials.merchantIds - apiUserCredentials.accountId
- [View a user](https://docs.nexiopay.com/reference/viewuser.md): FROM MANAGEMENT.JSON [ggg 2024-02-27] Keeping out of main API because WhoAmI is better and returns same parameters. Returns user information based on the provided ID. ## Request parameters - id ## Response parameters - userName - firstName - lastName - phone - enabled - notifications - accessRights - accessRights.merchantIds - accessRights.role - accountId - role - customAccess - cognitoSub - isEnabledForVTerm - shouldShowPlatformAgreement - shouldShowPricingAgreement - dateCreated - dateLastModified
- [View chargeback dispute](https://docs.nexiopay.com/reference/chargebackdispute.md): FROM REPORTING.JSON Returns a PDF of the chargeback dispute.
- [View statement summary](https://docs.nexiopay.com/reference/viewstatementsummary.md): FROM REPORTING.JSON Returns a summary PDF statement.
- [View adjustments](https://docs.nexiopay.com/reference/viewadjustments.md): FROM REPORTING.JSON Returns all adjustments within the given date range for all merchant IDs associated with the Nexio account used to [authenticate ](https://docs-beta.nexiopay.com/docs/getting-started/docs/authentication/authentication.md). You may also request or filter on fields of the query parameters, as in the following example: /report/v3/adjustments?kount.&plugin.&customer.&processor.&gateway. See the [query parameters ](https://docs-beta.nexiopay.com/docs/developer-tools/docs/apiTools/filter_query_parameters.md) section in Developer Tools for a full tutorial.
- [View a statement](https://docs.nexiopay.com/reference/viewstatement.md): FROM REPORTING.JSON Returns information on a single PDF statement.
- [View statements](https://docs.nexiopay.com/reference/viewstatements.md): FROM REPORTING.JSON Returns all adjustments within the given date range for all merchant IDs associated with the Nexio account used to [authenticate ](https://docs-beta.nexiopay.com/docs/getting-started/docs/authentication/authentication.md). You may also request or filter on fields of the query parameters, as in the following example: /report/v3/adjustments?kount.&plugin.&customer.&processor.&gateway. See the [query parameters ](https://docs-beta.nexiopay.com/docs/developer-tools/docs/apiTools/filter_query_parameters.md) section in Developer Tools for a full tutorial.
## Recipes
- [Configuring your backend server to listen for requests from the frontend](https://docs.nexiopay.com/recipes/configuring-your-backend-server-to-listen-for-requests-from-the-frontend.md)
- [Creating a product page that shows local currency and prices](https://docs.nexiopay.com/recipes/creating-a-product-page-that-shows-local-currency-and-prices.md)
- [Creating the checkout page with your own form](https://docs.nexiopay.com/recipes/creating-the-checkout-page-with-your-own-form.md)
- [Creating the confirmation page for payment success](https://docs.nexiopay.com/recipes/creating-the-confirmation-page-for-payment-success.md)
- [Creating the save card iframe page](https://docs.nexiopay.com/recipes/creating-the-save-card-iframe-page.md)
## Pages
- [Contact us](https://docs.nexiopay.com/page/contact-us.md)
- [License](https://docs.nexiopay.com/page/license.md)
## Changelog
- [Changelog for July 2025](https://docs.nexiopay.com/changelog/changelog-for-july-2025.md)
- [Changelog for June 2025](https://docs.nexiopay.com/changelog/changelog-for-june-2025.md)
- [Changelog for May 2025](https://docs.nexiopay.com/changelog/changelog-for-may-2025.md)
- [Changelog for March 2025](https://docs.nexiopay.com/changelog/changelog-for-march-2025.md)
- [Changelog for January 2025](https://docs.nexiopay.com/changelog/changelog-for-january-2025.md)
- [Changelog for December 2024](https://docs.nexiopay.com/changelog/changelog-for-december-2024.md)
- [Changelog for November 2024](https://docs.nexiopay.com/changelog/changelog-for-november-2024.md)
- [Changelog for October 2024](https://docs.nexiopay.com/changelog/changelog-for-october-2024.md)
- [Changelog for September 2024](https://docs.nexiopay.com/changelog/changelog-for-september-2024.md)
- [Changelog for August 2024](https://docs.nexiopay.com/changelog/changelog-for-august-2024.md)