ClubReady Api

<back to all web services

PaymentProfileUpdateEndpoint

The following routes are available for this service:
PUT/sales/wallet/paymentprofileupdateUpdate the personal information of a Payment ProfileOmitting 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:
NameParameterData TypeRequiredDescription
ApiKeybodystringYesGrants access to resources
AcctTokenbodystringYesAcctToken to update
ModifiedBybodyint?YesUserId that is updating profile
CcExpMonthbodybyte?NoExpiry Month: 1 = January, 12 = December
CcExpYearbodybyte?NoExpiry Year: Two digit year
FullNamebodystringNoThe name can be provided with FullName OR as separate fields (PrefixName, FirstName, MiddleName, LastName, SuffixName).
Providing both will cause an error.
PrefixNamebodystringNo
FirstNamebodystringNo
MiddleNamebodystringNo
LastNamebodystringNo
SuffixNamebodystringNo
Address1bodystringNo
Address2bodystringNo
UrbanizationbodystringNo
CitybodystringNo
StatebodystringNo
PostalCodebodystringNo
IsDisabledbodybool?NoDisable (or Enabled) the Payment Profile
ExcludeFromAcctUpdaterbodybool?NoExclude (or Include) from Account Updater
PaymentProfileUpdateRequestDto Parameters:
NameParameterData TypeRequiredDescription
AcctTokenformstringNo
ModifiedByformint?No
CcExpMonthformbyte?No
CcExpYearformbyte?No
FullNameformstringNo
PrefixNameformstringNo
FirstNameformstringNo
MiddleNameformstringNo
LastNameformstringNo
SuffixNameformstringNo
Address1formstringNo
Address2formstringNo
UrbanizationformstringNo
CityformstringNo
StateformstringNo
PostalCodeformstringNo
IsDisabledformbool?No
ExcludeFromAcctUpdaterformbool?No
ApiDtoBase Parameters:
NameParameterData TypeRequiredDescription
ApiKeyformstringNo
StoreIdformint?No
ChainIdformint?No
ApiResponseBase Parameters:
NameParameterData TypeRequiredDescription
SuccessformboolNo
MessageformstringNo

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: www.clubready.com 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"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","IsDisabled":false,"ExcludeFromAcctUpdater":false,"StoreId":0,"ChainId":0}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

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