ClubReady Api

PaymentProfileUpdateEndpoint

The following routes are available for this service:
PUT	/sales/wallet/paymentprofileupdate	Update the personal information of a Payment Profile	Omitting fields or providing `null` will not update that field. Providing an empty or whitespace string will remove the data from the field. To update the account information (Account Number, Last4, Country, etc), create a new Payment Profile.

**PaymentProfileUpdateEndpoint** Parameters:
Name	Parameter	Data Type	Required	Description
XForwardedFor	header	string	No	IP address of the end user
ApiKey	body	string	Yes	Grants access to resources
AcctToken	body	string	Yes	AcctToken to update
ModifiedBy	body	int?	Yes	UserId that is updating profile
CcExpMonth	body	byte?	No	Expiry Month: 1 = January, 12 = December
CcExpYear	body	byte?	No	Expiry Year: Two digit year
FullName	body	string	No	The name can be provided with FullName OR as separate fields (PrefixName, FirstName, MiddleName, LastName, SuffixName). Providing both will cause an error.
PrefixName	body	string	No
FirstName	body	string	No
MiddleName	body	string	No
LastName	body	string	No
SuffixName	body	string	No
Address1	body	string	No
Address2	body	string	No
Urbanization	body	string	No
City	body	string	No
State	body	string	No
PostalCode	body	string	No
CountryCode	body	string	No
IsDisabled	body	bool?	No	Disable (or Enabled) the Payment Profile
ExcludeFromAcctUpdater	body	bool?	No	Exclude (or Include) from Account Updater

**PaymentProfileUpdateRequestDto** Parameters:
Name	Parameter	Data Type	Required
AcctToken	form	string	No
ModifiedBy	form	int?	No
CcExpMonth	form	byte?	No
CcExpYear	form	byte?	No
FullName	form	string	No
PrefixName	form	string	No
FirstName	form	string	No
MiddleName	form	string	No
LastName	form	string	No
SuffixName	form	string	No
Address1	form	string	No
Address2	form	string	No
Urbanization	form	string	No
City	form	string	No
State	form	string	No
PostalCode	form	string	No
CountryCode	form	string	No
IsDisabled	form	bool?	No
ExcludeFromAcctUpdater	form	bool?	No

**ApiDtoBase** Parameters:
Name	Parameter	Data Type	Required
ApiKey	form	string	No
StoreId	form	int?	No
ChainId	form	int?	No

**ApiResponseBase** Parameters:
Name	Parameter	Data Type	Required	Description
Success	form	bool	No
Message	form	string	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

PUT /sales/wallet/paymentprofileupdate HTTP/1.1 
Host: clubready.com 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"XForwardedFor":"String","ApiKey":"String","AcctToken":"String","ModifiedBy":0,"CcExpMonth":0,"CcExpYear":0,"FullName":"String","PrefixName":"String","FirstName":"String","MiddleName":"String","LastName":"String","SuffixName":"String","Address1":"String","Address2":"String","Urbanization":"String","City":"String","State":"String","PostalCode":"String","CountryCode":"String","IsDisabled":false,"ExcludeFromAcctUpdater":false,"StoreId":0,"ChainId":0}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"Success":false,"Message":"String"}