You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been trying to setup a Schedule based on https://developer.heartlandpaymentsystems.com/Ecommerce/Recurring using a a tokenized credit card. I have managed to create a Schedule, but it never has an end date, nor a number of payments. I am using version 8.0.2.
What is the right way to set it up?
Here is the code I am using (I am changing the Schedule id on each request):
How am I supposed to set either the number of payments or the end date?
Why is the "Host Unavailable" error thrown? Is there a rate limit? Is there something else to consider?
What timezone are the start date and end date supposed to use?
Once a schedule gets created, is there a way to process the first payment right away? Or will the first payment be processed the next day the sooner?
Once a schedule gets created, is there a way to access information about the last payment processed? I see a paymentKey in the response. Is there an endpoint that can be used to get more information about the payment?
How are we supponsed to acknowledge that a payment was processed? Should we constantly query Schedule::findAll() or Schedule::find()?
The text was updated successfully, but these errors were encountered:
I have been trying to setup a Schedule based on https://developer.heartlandpaymentsystems.com/Ecommerce/Recurring using a a tokenized credit card. I have managed to create a Schedule, but it never has an end date, nor a number of payments. I am using version 8.0.2.
What is the right way to set it up?
Here is the code I am using (I am changing the Schedule id on each request):
I haven't found a way for making
$schedule->numberOfPaymentsRemaining
nor$schedule->endDate = $end_date
work.Sometimes I get schedules created, like the following:
Many other times I get errors like
Here are my questions about the integration:
The text was updated successfully, but these errors were encountered: