The Best Solution for Payment Processing in QuickBooks®

Today Payments is an Authorized Reseller of Intuit offering a highly robust app that supports both QuickBooks’ desktop and online customers, provide merchants with the tools they need so they can focus more time on their customers and businesses, and less time on data entry.
"Our Integrated payment solutions can save a typical small business owner more than 180 hours each year"
QuickBooks Pro Software QuickBooks Accounting Software Image
  • ~ Automate Account Receivable Collection
  • ~ Automate Account Payable Payments
  • ~ One-time and Recurring Debits / Credits

Secure QB Plugin payment processing through QuickBooks ® specializes in the origination of moving money electronically.

Ask about our special:

Request for Payments

Request For Payment (RFP) return codes in banking transactions may vary depending on the specific bank or financial institution. Return codes typically indicate issues with the processing of a payment request and may require action to resolve. Below are some generic examples of return codes that might be encountered during the receiving of funding transmissions for Request For Payment:

  1. Invalid Payee Information:
    • Description: The payee information provided in the Request For Payment is invalid or incomplete.
    • Action: Verify and update the payee information before attempting to resubmit the payment request.
  1. Insufficient Funds in Payer's Account:
    • Description: The payer's account does not have sufficient funds to cover the requested payment.
    • Action: Communicate with the payer to resolve the issue, request additional funds, or explore alternative payment methods.
  1. Invalid Payment Amount:
    • Description: The specified payment amount in the request is not valid or exceeds transaction limits.
    • Action: Verify the payment amount and ensure it adheres to the allowed limits.
  1. Duplicate Transaction:
    • Description: The Request For Payment is a duplicate of a previously processed transaction.
    • Action: Avoid resubmitting the same transaction; check for duplicates before initiating a new request.
  1. Invalid Request Format:
    • Description: The format of the request for payment does not meet the required standards.
    • Action: Ensure that the request adheres to the specified format and standards.
  1. Payment Reference Error:
    • Description: An error occurred with the payment reference or invoice number provided.
    • Action: Verify and correct the payment reference information.
  1. Payer Account Closed:
    • Description: The payer's account is closed, preventing the payment from being processed.
    • Action: Contact the payer and request updated account information.
  1. Bank Account Information Mismatch:
    • Description: The bank account information provided does not match the details on record.
    • Action: Verify and correct the bank account information.
  1. Payee Account Closed:
    • Description: The payee's account is closed, preventing the payment from being completed.
    • Action: Contact the payee and request updated account information.
  1. Payment Rejected by Payer:
    • Description: The payer explicitly rejected the payment request.
    • Action: Communicate with the payer to understand the reason for rejection and address any issues.
  1. Payment Timed Out:
    • Description: The payment request exceeded the allowed processing time.
    • Action: Review the processing time limits and ensure that payment requests are submitted within the specified timeframe.
  1. Technical Error:
    • Description: A technical error occurred during the processing of the payment request.
    • Action: Investigate the technical issue and resolve it before resubmitting the payment request.

Please note that these codes are illustrative, and actual return codes may vary. Consult the documentation provided by your bank or payment service provider for accurate and specific information on return codes associated with Request For Payment transactions. Additionally, ensure that the message data is thoroughly reviewed and cleaned before attempting to sync it into QuickBooks Online (QBO).

 
Request for Payment

Call us, the .csv and or .xml Request for Payment (RfP) file you need while on your 1st phone call! We guarantee our reports work to your Bank and Credit Union. We were years ahead of competitors recognizing the benefits of RequestForPayment.com. We are not a Bank. Our function as a role as an "Accounting System" in Open Banking with Real-Time Payments to work with Billers to create the Request for Payment to upload the Biller's Bank online platform. U.S. Companies need help to learn the RfP message delivering their bank. Today Payments' ISO 20022 Payment Initiation (PAIN .013) show how to implement Create Real-Time Payments Request for Payment File up front delivering message from the Creditor (Payee) to it's bank. Most banks (FIs) will deliver the message Import and Batch files for their company depositors for both FedNow and Real-Time Payments (RtP). Once uploaded correctly, the Creditor's (Payee's) bank continuing through a "Payment Hub", will be the RtP Hub will be The Clearing House, with messaging to the Debtor's (Payer's) bank.

Our in-house QuickBooks payments experts are standing ready to help you make an informed decision to move your company's payment processing forward.

Pricing with our Request For Payment Professionals
hand shake

 1) Free ISO 20022 Request for Payment File Formats, for FedNow and Real-Time Payments (The Clearing House) .pdf for you manually create "Mandatory" (Mandatory data for completed file) fields, start at page 4, with "yellow" highlighting. $0.0 + No Support


2) We create .csv or .xml formatting using your Bank or Credit Union. Create Multiple Templates. Payer/Customer Routing Transit and Deposit Account Number may be required to import with your bank. You can upload or "key data" into our software for File Creation of "Mandatory" general file.

Fees = $57 monthly, including Support Fees and Batch Fee, Monthly Fee, User Fee, Additional Payment Method on "Hosted Payment Page" (Request for file with an HTML link per transaction to "Hosted Payment Page" with ancillary payment methods of FedNow, RTP, ACH, Cards and many more!) + $.03 per Transaction + 1% percentage on gross dollar file,


3) Payer Routing Transit and Deposit Account Number is NOT required to import with your bank. We add your URI for each separate Payer transaction.

Fees Above 2) plus $29 monthly additional QuickBooks Online "QBO" formatting, and "Hosted Payment Page" and WYSIWYG


4)
Above 3) plus Create "Total" (over 600 Mandatory, Conditional & Optional fields of all ISO 20022 Pain .013) Price on quote.

Start using our Bank Reconciliation:

Request for Payment Bank Reconciliation

 Dynamic integrated with FedNow & Real-Time Payments (RtP) Bank Reconciliation: Accrual / Cash / QBO - Undeposited Funds




Give Us A Call

(866) 927-7180


Apply NOW

Stop Going to Your Bank to Deposit Checks!

Our office

Today Payments Merchant Services
2305 Historic Decatur Road, Suite 100
San Diego, CA 92106
(866) 927-7180