POST V1/FundingStatements.{ext}/RejectDebitPaymentFile

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.RejectDebitPayment
NameDescriptionTypeAdditional information
Action

No description available

string

None.

PFId

No description available

integer

None.

PFName

No description available

string

None.

RejectDebitPaymentDetail

No description available

Collection of EMS.Payments.Entities.RejectDebitPaymentDetail

None.

Request Formats

application/json, text/json

Sample:
{
  "action": "sample string 1",
  "pfId": 2,
  "pfName": "sample string 3",
  "rejectDebitPaymentDetail": [
    {
      "pfId": 1,
      "fsId": 2,
      "comments": "sample string 3"
    },
    {
      "pfId": 1,
      "fsId": 2,
      "comments": "sample string 3"
    }
  ]
}

application/xml, text/xml

Sample:
<RejectDebitPayment xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/EMS.Payments.Entities">
  <Action>sample string 1</Action>
  <PFId>2</PFId>
  <PFName>sample string 3</PFName>
  <RejectDebitPaymentDetail>
    <RejectDebitPaymentDetail>
      <Comments>sample string 3</Comments>
      <FSId>2</FSId>
      <PFId>1</PFId>
    </RejectDebitPaymentDetail>
    <RejectDebitPaymentDetail>
      <Comments>sample string 3</Comments>
      <FSId>2</FSId>
      <PFId>1</PFId>
    </RejectDebitPaymentDetail>
  </RejectDebitPaymentDetail>
</RejectDebitPayment>

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.