# Create or Update Batch SubPaymentMethod

Create or Update multiple SubPaymentMethod at once.  If the entity exists, it will be updated.  If the entity does not exist, it will be created.

Endpoint: PUT /subscribers/{subscriberID}/payment-methods-batch
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

  - `vbasoftware-database` (string, required)
    Target database

## Path parameters:

  - `subscriberID` (string, required)
    Subscriber ID

## Request fields (application/json):

  - `sub_Payment_Method_Key` (integer, required)
    The primary key and identifier of the record Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `acH_Pull_Day` (integer,null)
    Day of the month the ACH payment will be taken from the account

  - `benefit_Code` (string,null)
    References the benefit code associated with the payment method

  - `effective_Date` (string, required)
    The effective date of the payment method Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `entry_Date` (string)
    Date record was first added to the system

  - `entry_User` (string,null)
    User that first added the record to the system

  - `payment_Method` (string, required)
    The payment method associated with the subscriber, plan, benefit code combination

  - `plan_ID` (string,null)
    References the plan associated with the payment method

  - `subscriber_ID` (string, required)
    References the subscriber associated with the payment method

  - `term_Date` (string,null)
    The termination date of the payment method

  - `update_Date` (string)
    Date the record was last updated in the system

  - `update_User` (string,null)
    User that last updated the record in the system

## Response 207 fields (text/plain):

  - `data` (array,null)

  - `data.id` (array, required)
    List of key/value pairs that represent the unique id for the entity operation.

  - `data.id.key` (string,null)

  - `data.id.value` (any,null)

  - `data.status` (integer, required)
    http status of the operation (eg, 200, 201, 500)

  - `data.body` (string, required)
    operation message (eg, Updated, Created, Error message)

  - `error` (object)

  - `error.detail` (string,null)
    A human-readable explanation specific to this occurrence of the problem.

  - `error.instance` (string,null)
    A URI reference that identifies the specific occurrence of the problem.It may
or may not yield further information if dereferenced.

  - `error.status` (integer)
    The HTTP status code([RFC7231], Section 6) generated by the origin server for
this occurrence of the problem.

  - `error.title` (string,null)
    A short, human-readable summary of the problem type.It SHOULD NOT change from
occurrence to occurrence of the problem, except for purposes of localization(e.g.,
using proactive content negotiation; see[RFC7231], Section 3.4).

  - `error.type` (string,null)
    A URI reference [RFC3986] that identifies the problem type. This specification
encourages that, when dereferenced, it provide human-readable documentation for
the problem type (e.g., using HTML [W3C.REC-html5-20141028]). When this member
is not present, its value is assumed to be "about:blank".

  - `debug` (object)

  - `debug.activityID` (string, required)


## Response 401 fields