Integration and Testing

Authorize.Net API questions and help with your payment integration.

Posts: 12
Registered: ‎02-22-2016

Server receiving blank status from for ARB accounts (Gravity Forms)

Since setting up our WordPress (Gravity Forms) plugin to use ARB through each subscription is being returned by with a blank status, though it should be coming in as an active status.  Therefore, Gravity Forms is treating it as a failure.  But is still able to successfully charge each subscription monthly when the payment is due.  So says the subscription is active, but in our WordPress database, it's showing as failed and messing up our internal reporting.  Has anyone faced a similar situation?  Here is an example from our logs of one of those "failed" subscriptions:


2016-05-24 10:28:59.967730 - DEBUG --> GFAuthorizeNet::check_status(): Checking subscription status.
2016-05-24 10:28:59.976871 - DEBUG --> GFAuthorizeNet::check_status(): Lead with late payment => stdClass Object
[id] => 18970
[transaction_id] => XXXXXXXX
[payment_date] => 2016-04-25 18:55:37

2016-05-24 10:29:01.233449 - DEBUG --> GFAuthorizeNet::check_status(): Subscription ID => XXXXXXXX
2016-05-24 10:29:01.233575 - DEBUG --> GFAuthorizeNet::check_status(): Subscription Status =>
2016-05-24 10:29:01.233680 - DEBUG --> GFPaymentAddOn::fail_subscription_payment(): Processing request.
Posts: 2,765
Topics: 57
Kudos: 270
Blog Posts: 67
Registered: ‎12-05-2011

Re: Server receiving blank status from for ARB accounts (Gravity Forms)

Hello @hmhanson1316


This may be an issue you'll need to contact Gravity Forms to get help with.



Posts: 12
Registered: ‎02-22-2016

Re: Server receiving blank status from for ARB accounts (Gravity Forms)

Thanks Richard.  I have been in touch with Gravity Forms and they are stumped trying to find a fix.  I installed the Authorize.Net SDK onto my server and ran the sample get-subscription.php file.  The status was returned successfully, so I'm left to believe it's a Gravity Forms issue.


In the meantime, I was hoping that someone else had experienced this issue on Gravity Forms or a different solution and knew of some areas to check to resolve this issue.