We're currently using the Intuit SDK version 10 to sync to our app, we use /n software QuickBooks Integrator, and are querying QB for payments by QB Date Modified. We're experiencing random results from QB on returning payments, entered after our date trigger, the last modified date of the QB payment. We are wondering of there are actions in QB that can cause the payment modified date to be set to something other then the current date of the transaction which would cause them to be overlooked by the query.
Using QB 2012 Ent in this example,SDK 10,QBFC_10
Thanks,
Mark
Related
I used PayPal SDK to create and execute a billing agreement that was supposed to charge the client every 3 months.
However, I used the setup_fee to charge the customer immediately and set the start date to be 1 month in the future instead of 3.
I can see on the customer's profile that the customer next payment due date is in one month and I am not capable of changing the next payment date.
I've already tried using the billing agreement update method, but it doesn't let me change the start_date or next_payment_date.
Any idea how I can change the next payment date for the existing billing agreement that have already been executed?
The answer is not great, but the somewhat solution I found was to suspend the plans.
To give more context, my problem was the following:
User subscribed to quarterly paid plan on September 15th and paid setup_fee
Next payment was incorrectly configured to be on October 15th - because I added a month to the start date*
The actual next payment date should be 3 months after, on December 15h
My "solution":
I paused the subscriptions for those users before October 15th, more specifically on October 10th.
I restarted the solution 2 days after the incorrect next_payment_date, on October 17th.
Once the plan was restarted the next_payment_date was set to 3 months later, so it was set to January 15th.
So as you can observe, I was not able to actually fix it, but rather I accepted to "lose" a month.
Note: Paypal support was LESS than useful. At first their recommendation was to cancel the plan and ask the users to buy again. Then I sugggested the approach of suspending and they INCORRECTLY confirmed to me that the next payment date would be the correct one, and that was not true, it was ONE month later. So be aware of what their support says.
We are planning to integrate to PayPal with following requirements:
We collect card based payments for US customers.
We are planning to integrate with Payflow Gateway with "Sage" as our processor.
We will have customers who will allow us to charge them on a periodic
basis (replenishment with Card on file).
Questions:
Is Payflow Gateway suitable for our requirements?
Does Payflow Gateway has a REST based interface? How do we tokenize (card on file) without keeping card numbers with us?
If "reference transaction" is the only way to do Card on file operation, how do we overcome the expiry period (1 year) of referenced transaction?
Payflow will do this through the reference transaction feature. For a reference transaction, you will be storing the transaction ID in your database, and the next time you want to charge the customer you will use the same transaction ID instead of passing the card details again.
Usually any transaction ID at Payflow is valid for one year, as per the docs. So in order to overcome that one year restriction, you are supposed to update your database every time with the latest transaction ID.
For example, a customer placed an order today, and you store the Payflow transaction ID in the database. Now suppose you need to charge the customer again after 7 months, then you will get a new transaction ID. This time, update your database with the new transaction ID for the same customer, and this way it will be valid again for another year.
You can do reference transactions (using the returned PNREF) but, like you said, they expire in 1 year. The only workaround for this I've found is to issue a zero-dollar authorization (ZDA) to get a new PNREF but there is some confusion about this with some reports saying that the new PNREF created by the ZDA will only work for 14 days.
The online version of the Payflow Pro Guide now states that the PNREF is good for reference transactions for "12 months and possibly up to 15 months". Unfortunately, that is pretty ambiguous wording that doesn't clear up very much.
PayPal newbie. Is there a way to schedule multiple (somewhat random) payments with the PayPal Rest API? The application I'm building has a weekly fee for participation in an activity. The caveat is that some weeks are canceled due to holidays or other unforeseen reasons.
So, for a given month like September 2015, a customer may want to pay for the entire month of "valid dates" in that month. I may need to schedule the following payments:
9/1/2015, 9/8/2015, 9/15/2015, and 9/29/2015. (skipping 9/22/2015).
At this point, I do not see this capability with recurring payments. Maybe a transaction with a future billing date?
I would recommend using the classic API for now. It's still much further along than REST.
You could use Preapproval and Pay or you could use Express Checkout and/or Payments Pro with reference transactions.
If you happen to be working with PHP this PayPal PHP SDK will make the API calls to get that done very quick and easy for you.
I want to use subscriptions as a business model (https://developers.facebook.com/docs/payments/subscriptions/) but for onetime payment (Upgrading from lite to full version). The problem is that the metadata“fbpayment:billing_period” in fbpayment:subscription object takes "1 month" as default while the user in my app need to pay one time only to upgrade his version .
Also the subscription dialog shows the price of subscription per month which is not real in my case.
My aim for using subscriptions is to use Graph API for querying the subscription status and know who is already subscriber to give him access for specific materials . The regular payment follow in this tutorial: https://developers.facebook.com/docs/howtos/payments/paymentflow, doesn't tell how to retrieval these records .
My question is that how to use subscriptions for onetime payment ?
Payment via PayPal credit/debit cards apparently ceased to function entirely on my website since a month ago.
I see the version specified in the code is 94.0 whereas the current version is (99.0). Can this be the reason why payments don't work anymore?