# Update SubPaymentMethod Updates a specific SubPaymentMethod. Endpoint: PUT /subscribers/{subscriberID}/payment-methods/{subPaymentMethodKey} Version: v1 Security: apiKeyAuth, bearerAuth ## Header parameters: - `vbasoftware-database` (string, required) Target database ## Path parameters: - `subscriberID` (string, required) Subscriber ID - `subPaymentMethodKey` (integer, required) Sub Payment Method Key ## 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 200 fields (text/plain): - `data` (object) - `data.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. - `data.acH_Pull_Day` (integer,null) Day of the month the ACH payment will be taken from the account - `data.benefit_Code` (string,null) References the benefit code associated with the payment method - `data.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. - `data.entry_Date` (string) Date record was first added to the system - `data.entry_User` (string,null) User that first added the record to the system - `data.payment_Method` (string, required) The payment method associated with the subscriber, plan, benefit code combination - `data.plan_ID` (string,null) References the plan associated with the payment method - `data.subscriber_ID` (string, required) References the subscriber associated with the payment method - `data.term_Date` (string,null) The termination date of the payment method - `data.update_Date` (string) Date the record was last updated in the system - `data.update_User` (string,null) User that last updated the record in the system - `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