topic settingName 'merchant' is rejected in Integration and Testing

settingName 'merchant' is rejected

winternet — Fri, 14 Nov 2014 13:51:48 GMT

According to page 77 in http://www.authorize.net/support/AIM_guide_XML.pdf I can specify a setting named "merchant" to cause an e-mail to be sent to me as merchant (in addition to what may be specified in the merchant web interface). It says:

"To send a confirmation to the merchant, add another settingName element with the
value merchant, and set the value to the email address to which the merchant’s copy
of the customer confirmation email should be sent. If a value is submitted, an email
will be sent to this address as well as the address(es) configured in the Merchant
Interface."

But when I try to include this:

...

<settingName>merchant</settingName>

<settingValue>my@email.com</settingValue>

</setting>

...

...I get the following response:

"Setting Name 'merchant' is invalid for this method."

Re: settingName 'merchant' is rejected

RichardH — Sat, 15 Nov 2014 02:58:06 GMT

Hello @winternet

Would you mind sharing your entire request with sensitive information redacted so we further troubleshoot?

Richard

Re: settingName 'merchant' is rejected

winternet — Mon, 17 Nov 2014 08:23:51 GMT

Sure, here you go:

<?xml version="1.0" encoding="UTF-8"?>
<createTransactionRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <merchantAuthentication>
      <name>xxxxxxxxxxxxx</name>
      <transactionKey>xxxxxxxxxxxxxx</transactionKey>
   </merchantAuthentication>
   <transactionRequest>
      <transactionType>authCaptureTransaction</transactionType>
      <amount>285.00</amount>
      <payment>
         <creditCard>
            <cardNumber>370000000000002</cardNumber>
            <expirationDate>05/15</expirationDate>
            <cardCode>123</cardCode>
         </creditCard>
      </payment>
      <profile>
         <createProfile>true</createProfile>
      </profile>
      <order>
         <invoiceNumber>5006</invoiceNumber>
         <description>Test of 2014-11-17 09:19:59</description>
      </order>
      <customer>
         <id>ID451</id>
         <email>test@test.com</email>
      </customer>
      <billTo>
         <firstName>John</firstName>
         <lastName>Doe</lastName>
         <company>WinterNet Studio</company>
         <address>450 Upper St.</address>
         <city>OurCity</city>
         <state>NC</state>
         <zip>54465</zip>
         <country>US</country>
         <phoneNumber>655-464-1131</phoneNumber>
      </billTo>
      <customerIP>174.54.54.97</customerIP>
      <transactionSettings>
         <setting>
            <settingName>emailCustomer</settingName>
            <settingValue>true</settingValue>
         </setting>
         <setting>
            <settingName>duplicateWindow</settingName>
            <settingValue>10</settingValue>
         </setting>
         <setting>
            <settingName>merchant</settingName>
            <settingValue>email@merchant.com</settingValue>
         </setting>
      </transactionSettings>
   </transactionRequest>
</createTransactionRequest>

Re: settingName 'merchant' is rejected

RaynorC1emen7 — Mon, 17 Nov 2014 13:43:37 GMT

look like the xml doc is incorrect

from the schema https://api.authorize.net/xml/v1/schema/AnetApiSchema.xsd

Allowed values for settingName are: emailCustomer, merchantEmail, allowPartialAuth, headerEmailReceipt, footerEmailReceipt, recurringBilling, duplicateWindow, testRequest.

Re: settingName 'merchant' is rejected

winternet — Tue, 18 Nov 2014 09:50:26 GMT

Ok, it works with 'merchantEmail'. It was just the above mentioned error in the PDF that confused me then.