POST V1/FundingStatements.{ext}/GenerateDebitACHPaymentFile

Request Information

URI Parameters

NameDescriptionTypeAdditional information
ext

Which media types are acceptable for the response, such as json/xml

If no matches are found, the content negotiator tries to match on the media type of the request body, if any. For example, if the request contains JSON data, the content negotiator looks for a JSON formatter.

string

Content-Type: application/json OR application/xml

Body Parameters

EMS.Payments.Entities.ACHPaymentFile
NameDescriptionTypeAdditional information
PaymentFileDate

No description available

string

None.

CompanyCode

No description available

string

None.

CurrencyCode

No description available

string

None.

CompanyId

No description available

string

None.

DebitPaymentFileDetailList

No description available

Collection of EMS.Payments.Entities.DebitPaymentFileDetail

None.

Request Formats

application/json, text/json

Sample:
{
  "paymentFileDate": "sample string 1",
  "companyCode": "sample string 2",
  "currencyCode": "sample string 3",
  "companyId": "sample string 4",
  "debitPaymentFileDetailList": [
    {
      "fsId": 1,
      "comments": "sample string 2",
      "clientId": 3
    },
    {
      "fsId": 1,
      "comments": "sample string 2",
      "clientId": 3
    }
  ]
}

application/xml, text/xml

Sample:
<ACHPaymentFile xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/EMS.Payments.Entities">
  <CompanyCode>sample string 2</CompanyCode>
  <CompanyId>sample string 4</CompanyId>
  <CurrencyCode>sample string 3</CurrencyCode>
  <DebitPaymentFileDetailList>
    <DebitPaymentFileDetail>
      <ClientId>3</ClientId>
      <Comments>sample string 2</Comments>
      <FSId>1</FSId>
    </DebitPaymentFileDetail>
    <DebitPaymentFileDetail>
      <ClientId>3</ClientId>
      <Comments>sample string 2</Comments>
      <FSId>1</FSId>
    </DebitPaymentFileDetail>
  </DebitPaymentFileDetailList>
  <PaymentFileDate>sample string 1</PaymentFileDate>
</ACHPaymentFile>

application/x-www-form-urlencoded

Sample:

Sample not available.

application/bson

Sample:
Binary JSON content. See http://bsonspec.org for details.

Response Information

Resource Description

EMSResponseOfEMS.Common.TransactionResults
NameDescriptionTypeAdditional information
ResponseType

No description available

string

None.

Response

No description available

EMS.Common.TransactionResults

None.

Error

No description available

EMS.Common.Error

None.

Response Formats

application/json, text/json

Sample:
{
  "responseType": "TransactionResults",
  "response": {
    "transactionResult": [
      {
        "status": "sample string 1",
        "message": "sample string 2",
        "result": "sample string 3"
      },
      {
        "status": "sample string 1",
        "message": "sample string 2",
        "result": "sample string 3"
      }
    ]
  },
  "error": {
    "errorCode": "sample string 1",
    "errorDescription": "sample string 2"
  }
}

application/bson

Sample:
Binary JSON content. See http://bsonspec.org for details.