Custom data

If you send or validate a payment with the ACH Origination API or the Wire Origination API, you can add information to the customData in the request payload.

Custom data is client-specific metadata that you can:

• Use to append certain information or details
• Use as an identifier to filter certain types of transactions

The customData information is not transmitted with the payment or stored in any KeyBank database. This information is only visible to you, the originator, with the ACH Inquiry API or the Wire Inquiry API. In the inquiry response, the customData field returns any custom values that were part of the payment request stored for recall after a successful ACH or wire transaction completes. This information is not visible to the recipient or any of the participating parties.

Here's how it works

1. Define the customData in the request payload. It is a free-form text field that can contain up to 500 alphanumeric characters that you can use however you like - for invoice number, product number, customer number, date/time stamp, etc.

   KeyBank recommends the common custom data format of name-value pairs. You can list multiple name-value pairs in the custom data field within the 500-character limit. The custom data fields will return exactly what is sent; it does not parse name-value pairs within the API response. The custom data should not contain any personal identifiable information (PII).

   Custom data examples

   //Example of name:value pairs
   "customData": "Type:DD; Status:Submitted; POnumber:12556"
   
   //Example of regular text
   "customData": "General products"
   
   //Example of timestamp
   "customData": "05-MAR-2023:12:19:53EST"
   
   

    

2. As the originator, you can use the ACH Inquiry API or Wire Inquiry API to retrieve the custom data information.

3. Review the response for the customData field.

   • If there is custom data, it returns any custom values that were part of the payment request stored for recall after a successful ACH or wire transaction completes.
   • If no custom data is defined, the response returns an empty field.