This section addresses common questions about merchant account setup and processing in Admoji. These Q&A items will help you understand how to properly configure your merchant accounts and payment processors.
Q: Is a merchant account needed to process credit cards?
A: Yes, a merchant account is required to process live credit card transactions. Admoji integrates with many major merchant account providers and gateways. If you need help obtaining a merchant account, contact our support team for assistance with integrations.
A: Yes, a merchant account is required to process live credit card transactions. Admoji integrates with many major merchant account providers and gateways. If you need help obtaining a merchant account, contact our support team for assistance with integrations.
Q: How do I setup Square processing?
A: Three steps: 1. Go to Merchants > Processors, click New while on the Credit Card tab, then select Square from the Gateway dropdown and enter your Access Token. Disable the Test Mode toggle for live merchant accounts. 2. Square requires using their payment form on your website. Refer to the API documentation for integration details. 3. Select the Square processor to be used within the campaign's Processors tab.
A: Three steps: 1. Go to Merchants > Processors, click New while on the Credit Card tab, then select Square from the Gateway dropdown and enter your Access Token. Disable the Test Mode toggle for live merchant accounts. 2. Square requires using their payment form on your website. Refer to the API documentation for integration details. 3. Select the Square processor to be used within the campaign's Processors tab.
Q: How do I setup Authorize.net?
A: Go to Merchants > Processors and click New. Select Authorize.net from the Gateway dropdown within the Credit Card tab. Enter your Api Login ID and Transaction Key from your Authorize.net account in the credentials fields. Fill in Processor Name, Merchant ID (optional), Descriptor (optional), MID Number, Monthly Limit, and other settings as needed. Disable the Test Mode toggle for live merchant accounts. While Test Mode is on, transactions go to the Authorize.net sandbox with the credentials you entered, so use the Api Login ID and Transaction Key of your Authorize.net sandbox account. Authorize.net supports Auth + Capture: set Transaction Mode on the Settings tab (see How to Set Up Auth + Capture).
A: Go to Merchants > Processors and click New. Select Authorize.net from the Gateway dropdown within the Credit Card tab. Enter your Api Login ID and Transaction Key from your Authorize.net account in the credentials fields. Fill in Processor Name, Merchant ID (optional), Descriptor (optional), MID Number, Monthly Limit, and other settings as needed. Disable the Test Mode toggle for live merchant accounts. While Test Mode is on, transactions go to the Authorize.net sandbox with the credentials you entered, so use the Api Login ID and Transaction Key of your Authorize.net sandbox account. Authorize.net supports Auth + Capture: set Transaction Mode on the Settings tab (see How to Set Up Auth + Capture).
Q: Why can't I refund orders when I process with Authorize.net?
A: Authorize.net and other merchant accounts that use Authorize.net as their background processing have strict rules regarding when refunds can be issued:
You can only refund a transaction that has been previously authorized using the payment gateway.
The original transaction must have a status of Settled Successfully. You cannot issue refunds against unsettled, voided, declined, or error transactions.
The refund transaction must be issued within 120 days of the date the original transaction was settled.
A refund transaction cannot exceed the amount of the original transaction.
The payment method provided in the refund transaction must match the payment method that was provided in the original transaction. You must provide the last four digits of a masked credit card or bank account number from the original transaction.
If the processor uses Auth + Capture and the authorization has not been captured yet, Admoji offers Void instead of a refund.
A: Authorize.net and other merchant accounts that use Authorize.net as their background processing have strict rules regarding when refunds can be issued:
You can only refund a transaction that has been previously authorized using the payment gateway.
The original transaction must have a status of Settled Successfully. You cannot issue refunds against unsettled, voided, declined, or error transactions.
The refund transaction must be issued within 120 days of the date the original transaction was settled.
A refund transaction cannot exceed the amount of the original transaction.
The payment method provided in the refund transaction must match the payment method that was provided in the original transaction. You must provide the last four digits of a masked credit card or bank account number from the original transaction.
If the processor uses Auth + Capture and the authorization has not been captured yet, Admoji offers Void instead of a refund.
Q: What is the difference between PayPal Checkout vs PayPal Payflow Pro?
A: PayPal Checkout, shown as PayPal Expanded in the Gateway dropdown, requires API integration on your website. Customers are redirected to PayPal to complete the transaction, then return to your thank you page. It uses Client ID and Client Secret as credentials. PayPal Payflow Pro functions like a standard credit card processor and doesn't require extra API coding on your site. It uses Username, Password, Merchant, and Partner as credentials. For more information, refer to the Payflow Gateway documentation. If you want PayPal to process cards without a redirect using Client ID and Client Secret, choose PayPal Commerce.
A: PayPal Checkout, shown as PayPal Expanded in the Gateway dropdown, requires API integration on your website. Customers are redirected to PayPal to complete the transaction, then return to your thank you page. It uses Client ID and Client Secret as credentials. PayPal Payflow Pro functions like a standard credit card processor and doesn't require extra API coding on your site. It uses Username, Password, Merchant, and Partner as credentials. For more information, refer to the Payflow Gateway documentation. If you want PayPal to process cards without a redirect using Client ID and Client Secret, choose PayPal Commerce.
Q: How do I add merchant accounts?
A: Go to Merchants > Processors and click New. Select the desired tab (Credit Card or ACH), then choose a gateway from the Gateway dropdown. Enter the required credentials and fill in the Settings fields (Processor Name, Descriptor, MID Number, Monthly Limit, Currency, etc.). Disable the Test Mode toggle for live merchant accounts, then save.
A: Go to Merchants > Processors and click New. Select the desired tab (Credit Card or ACH), then choose a gateway from the Gateway dropdown. Enter the required credentials and fill in the Settings fields (Processor Name, Descriptor, MID Number, Monthly Limit, Currency, etc.). Disable the Test Mode toggle for live merchant accounts, then save.
Q: How do I delete a processor or merchant account?
A: Processors cannot be deleted but can be deactivated. On the Processors page (Merchants > Processors), click the Edit Processor action (pencil icon) in the Actions column. In the edit form, scroll to the Options section and toggle the Active switch off, then save to deactivate the processor.
A: Processors cannot be deleted but can be deactivated. On the Processors page (Merchants > Processors), click the Edit Processor action (pencil icon) in the Actions column. In the edit form, scroll to the Options section and toggle the Active switch off, then save to deactivate the processor.
Q: Can I setup alerts for merchant account limits?
A: Yes. Alerts can be set up for merchant account limits, refunds, declines, and chargebacks. Whether you need to be alerted when you hit your limits, or when you have excess refunds or decline transactions, the alert system will report on each activity. For more information, refer to Alert System.
A: Yes. Alerts can be set up for merchant account limits, refunds, declines, and chargebacks. Whether you need to be alerted when you hit your limits, or when you have excess refunds or decline transactions, the alert system will report on each activity. For more information, refer to Alert System.
Q: Can I limit the processing amount for my merchant account?
A: Yes. You can set a Monthly Limit in the processor's Settings. Go to Merchants > Processors, click the Edit Processor action (pencil icon), and enter the desired cap amount in the Monthly Limit field. Enter 0 to disable the cap (unlimited).
The Monthly Limit is checked when a charge goes to that specific MID, for example a rebill or upsell on a sticky processor, or a forced processor. When the MID has reached it, Admoji sends the charge through the load balancer instead. New orders routed by the load balancer use the Day cap and Month cap of the rule in Merchants > Management, so set the cap there too.
A: Yes. You can set a Monthly Limit in the processor's Settings. Go to Merchants > Processors, click the Edit Processor action (pencil icon), and enter the desired cap amount in the Monthly Limit field. Enter 0 to disable the cap (unlimited).
The Monthly Limit is checked when a charge goes to that specific MID, for example a rebill or upsell on a sticky processor, or a forced processor. When the MID has reached it, Admoji sends the charge through the load balancer instead. New orders routed by the load balancer use the Day cap and Month cap of the rule in Merchants > Management, so set the cap there too.