-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authorize.Net Expiration Date Format #576
Comments
jaswrks
pushed a commit
to wpsharks/s2member-pro
that referenced
this issue
May 21, 2015
jaswrks
pushed a commit
to wpsharks/s2member-pro
that referenced
this issue
May 21, 2015
jaswrks
pushed a commit
to wpsharks/s2member-pro
that referenced
this issue
May 21, 2015
Next Release Changelog:
|
Short-Term Patch Instructions
|
The latest release of s2Member v150722+ closes this issue. This issue will now be locked to further updates. If you have something to add related to this GitHub Issue, please open a new GitHub Issue and reference this one. Thanks! :-) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Referencing internal ticket:
https://websharks.zendesk.com/agent/tickets/6448
@raamdev writes...
Two Different Formats (AIM vs. ARB)
Authorize.Net has two different formats it seems.
The AIM docs here ask for
MM-YYYY
http://developer.authorize.net/api/reference/#payment-transactions
I'm guessing this has previously accepted
YYYY-MM
also, but something changed recently.The ARB docs here ask for
YYYY-MM
http://developer.authorize.net/api/reference/#recurring-billing-create-a-subscription
The text was updated successfully, but these errors were encountered: