Syntch Gateway API

<back to all web services

PatchCustomField

Administration - Custom Field Management
Requires Authentication
Requires the role:Merchant
The following routes are available for this service:
PATCH/customfields/{Key}Updates a single custom field for the merchant requester with only the data provided.
PatchCustomField Parameters:
NameParameterData TypeRequiredDescription
KeypathintYesThe key of the custom field to be edited.
NamemodelstringNoThe name of the custom field. Cannot exceed 50 characters. Should be unique.
IsNumericmodelbool?NoIndicates the IsNumeric value for the field.
DecimalPlacesmodelint?NoIndicates the number of decimal places for the field (used with numeric fields).
RegularExpressionmodelstringNoIndicates the regular expression value for the field.
IsRequiredmodelbool?NoIndicates if the field is required.
ActivationStatusmodelActivationStatus?NoIndicates the initial activation status value for the field.

Allowable Values

  • Pending
  • Active
  • Inactive
  • Deleted
DescriptionmodelstringNoIndicates the description value for the field. Cannot exceed 50 characters.
ErrorMessagemodelstringNoIndicates the error message value for the field. Cannot exceed 50 characters.
MinValuemodeldouble?NoIndicates the minimum numeric value for the field (used with numeric fields).
MaxValuemodeldouble?NoIndicates the minimum numeric value for the field (used with numeric fields).
MaxLengthmodelint?NoIndicates the maximum text length value for the field (used with non-numeric fields).
Positionmodelint?NoIndicates the position value for the field.
DisplayOnVTReceiptmodelbool?NoIndicates if the field should be displayed on virtual terminal receipt.
DisplayOnReportsmodelbool?NoIndicates if the field should be displayed on reports.
DisplayOnHppmodelbool?NoIndicates if the field should be displayed on the hosted payments page.
ReadOnlyOnHppmodelbool?NoIndicates if the field should not be editable on the hosted payments page.
VisibleOnHppmodelbool?NoIndicates if the field should be visible on the hosted payments page.
ActivationStatus Enum:
Pending
Active
Inactive
Deleted
CustomFieldResponse Parameters:
NameParameterData TypeRequiredDescription
KeymodelintNoThe unique identifier of the custom field.
NamemodelstringNoThe name of the custom field. Cannot exceed 50 characters. Should be unique.
MerchantKeymodelintNoThe key of the merchant that has this custom field.
IsNumericmodelboolNoIndicates if the field is numeric.
DecimalPlacesmodelint?NoIndicates the number of decimal places.
RegularExpressionmodelstringNoA validation expression.
IsRequiredmodelbool?NoIndicates if the field should be required input.
ActivationStatusmodelActivationStatusNoIndicates the activation status of the field.

Allowable Values

  • Pending
  • Active
  • Inactive
  • Deleted
DescriptionmodelstringNoThe description of the field.
ErrorMessagemodelstringNoIndicates the validation error message of the field.
MinValuemodeldouble?NoIndicates the minimum numeric value of the field.
MaxValuemodeldouble?NoIndicates the maximum numeric value of the field.
MaxLengthmodelint?NoIndicates the maximum character length of the field.
PositionmodelintNoIndicates the position the field, relative to other custom fields being displayed.
DisplayOnVTReceiptmodelbool?NoIndicates if the field is displayed on VT receipts.
DisplayOnReportsmodelbool?NoIndicates if the field is displayed on reports.
DisplayOnHppmodelbool?NoIndicates if the field is displayed on the HPP.
ReadOnlyOnHppmodelbool?NoIndicates if the field is read-only on the HPP.
VisibleOnHppmodelbool?NoIndicates if the field is visible on the HPP.

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

HTTP + XML

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

PATCH /customfields/{Key} HTTP/1.1 
Host: syntch.simpay.net 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<PatchCustomField xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Gateway.RestApi.CustomFields.Requests">
  <ActivationStatus>Pending</ActivationStatus>
  <DecimalPlaces>0</DecimalPlaces>
  <Description>String</Description>
  <DisplayOnHpp>false</DisplayOnHpp>
  <DisplayOnReports>false</DisplayOnReports>
  <DisplayOnVTReceipt>false</DisplayOnVTReceipt>
  <ErrorMessage>String</ErrorMessage>
  <IsNumeric>false</IsNumeric>
  <IsRequired>false</IsRequired>
  <Key>0</Key>
  <MaxLength>0</MaxLength>
  <MaxValue>0</MaxValue>
  <MinValue>0</MinValue>
  <Name>String</Name>
  <Position>0</Position>
  <ReadOnlyOnHpp>false</ReadOnlyOnHpp>
  <RegularExpression>String</RegularExpression>
  <VisibleOnHpp>false</VisibleOnHpp>
</PatchCustomField>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<CustomFieldResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Gateway.RestApi.CustomFields.Responses">
  <ActivationStatus>Pending</ActivationStatus>
  <DecimalPlaces>0</DecimalPlaces>
  <Description>String</Description>
  <DisplayOnHpp>false</DisplayOnHpp>
  <DisplayOnReports>false</DisplayOnReports>
  <DisplayOnVTReceipt>false</DisplayOnVTReceipt>
  <ErrorMessage>String</ErrorMessage>
  <IsNumeric>false</IsNumeric>
  <IsRequired>false</IsRequired>
  <Key>0</Key>
  <MaxLength>0</MaxLength>
  <MaxValue>0</MaxValue>
  <MerchantKey>0</MerchantKey>
  <MinValue>0</MinValue>
  <Name>String</Name>
  <Position>0</Position>
  <ReadOnlyOnHpp>false</ReadOnlyOnHpp>
  <RegularExpression>String</RegularExpression>
  <VisibleOnHpp>false</VisibleOnHpp>
</CustomFieldResponse>