The fields and formats needed for the EditCustomerPaymentDay conversation are listed in this section.
Brokers have a way to modify a customer's payment date with the EditCustomerPaymentDay request. The request is verified, and any inaccuracies are returned for correction.


Method	POST
url	/editcustomerpaymentday

Request example

{
    "clientCode": "CC",
    "shopCode": "XXXX",
    "EditCustomerPaymentDayRequestType":{
        "BrokerReference": "3607\/009",
        "accountNumber":"910000016970",
        "PreferredPaymentDay":1
        
    }
}

Response example

{
    "data": {
        "editCustomerPaymentDayResponseType": {
            "responseStatus": 1,
            "responseStatusText": "Success"
        },
        "errors": null
    },
    "validationErrors": [],
    "error": -1,
    "error_description": null,
    "successful": true
}

Fields

EditCustomerPaymentDayRequestType

Node	Required	Type	Max Length	Notes
BrokerReference	Mandatory	String	25	This is a unique reference provided by the broker to identify the applicant. The broker can use this reference to identify and locate the applicant on the BNPP PF system.

AccountNumber	Mandatory	String	15	This is the reference BNPP PF has assigned to the applicant as part of the new application process. It is used to locate the account and apply the transaction. It is mandatory to provide the AccountNumber and BrokerReference for EditCustomerPaymentDayReq uest.
PreferredPaymentDay	Mandatory	Integer		This is the applicant's preferred payment day. BNPP PF accepts 1-28. If 0 is entered, then this is used in conjunction with the inception date (Must be pre- approved by BNPP PF). On renewal, BNPP PF uses the existing preferred payment day. This value will not be used for renewals.

EditCustomerPaymentDayResponseType

Node	Required	Type	Max Length	Notes
ResponseStatus	Mandatory	Enum		This is the status of a response See ResponseStatus in Option Values