Body: <p>We are switching to Authorize.net as payment processor.  The Invoice ID in CiviCRM is 32 characters.  However, Authorize.net's Invoice Number field is only 20 characters.  The Invoice ID when passed to Authorize.net is getting truncated.  Can the Invoice ID in Civi be shortened? to 20 characters?  If so, what is the impact on existing transactions?</p>
  
  <p>We are currently on Civi 4.6 but will be upgrading to 4.7 within the next 2 months. On Drupal 7.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-01-31T22:24:43.267Z
Comments.Text: Not a solution but we are also using authnet with civiCRM 4.7 and for online contributions we just use the 10 character "transaction ID" to match from authnet to civicrm instead. Without having much information on the use-case it seems like this might work.
Comments.UserDisplayName: Eli Lisseck
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-01-31T23:02:45.567Z
Comments.Text: I missed the transaction ID.  That is event better than the invoice number and it connects everything up.
Comments.UserDisplayName: Ron Gridley
Tags: <payment-processor><authorize.net>
Title: Authorize.net Invoice ID Field Length
ThreadText: # Authorize.net Invoice ID Field Length
  
  (Asked by: username_0 on 2017-01-31)
  
  We are switching to Authorize.net as payment processor. The Invoice ID in CiviCRM is 32 characters. However, Authorize.net's Invoice Number field is only 20 characters. The Invoice ID when passed to Authorize.net is getting truncated. Can the Invoice ID in Civi be shortened? to 20 characters? If so, what is the impact on existing transactions?
  
  We are currently on Civi 4.6 but will be upgrading to 4.7 within the next 2 months. On Drupal 7.
  
  **Tags:** payment-processor, authorize.net
  
  > **Comments:**
  > **username_1**: Not a solution but we are also using authnet with civiCRM 4.7 and for online contributions we just use the 10 character "transaction ID" to match from authnet to civicrm instead. Without having much information on the use-case it seems like this might work.  
  > **username_0**: I missed the transaction ID.  That is event better than the invoice number and it connects everything up.  
  
  ---
  
  ## 0 answers
  
  