Comments (8)
It only supports the common functions at the moment - authorisation, payments, capture, but not much else. There are no plans to extend that, but that does not mean it can't or won't be supported if someone wants (or has a need) to put the time in.
from omnipay-authorizenet.
We'd be happy to help out with adding some of that functionality. I'll take a closer look at the project and see where/when we might be able to help out.
from omnipay-authorizenet.
Have a look at some of the other gateways that implement some kind of recurring billing feature (e.g. PayPal REST, Stripe, etc) and make sure that you use roughly the same method names. Recurring billing specifically is outside of the scope of Omnipay but there are a few gateways that have added it.
from omnipay-authorizenet.
Been looking at the way Authorize.Net is going, and it seems that they are in the process of deprecating all their current integration-oriented APIs. Instead, they are pulling all the functionality into a merchant-oriented API, based largely on the original AIM API.
I think if starting again here, it would be good to follow the way they have structured the new API, with focus on groups of functions for:
- Transactions
- Customer profiles
- Recurring billing <-- this is the one you are asking about
- Reporting
So in this case rather than, say, firing up an AIM gateway object and doing recurring billing through it, you would instantiate a "recurring billing" gateway object and do all the recurring billing stuff you may need to do through that. You may also need to instantiate customer profiles and transactions objects to work in conjunction with that (e.g. a recurring bill would need a customer profile to work from).
I think also now that the API fully supports JSON, that should be used as it is easier to handle (the XML objects can be a bit cumbersome at times).
from omnipay-authorizenet.
And using something like dot notation to access the received data would be so much easier than having to check for missing elements constantly:
https://github.com/dflydev/dflydev-dot-access-data
from omnipay-authorizenet.
I'm not quite sure they have the JSON API quite right yet. The documentation gives examples with fragments in similar to this:
"lineItems": {
"lineItem": {
"itemId": "1",
"name": "vase",
"description": "Cannes logo",
"quantity": "18",
"unitPrice": "45.00"
}
},
That's okay for XML, where multiple lineItem
elements can be child elements of the lineItems
element. But this does not work in JSON, so I guess the documentation is incorrect and this should be an array, perhaps something like this:
"lineItems": [
{
"itemId": "1",
"name": "vase",
"description": "Cannes logo",
"quantity": "18",
"unitPrice": "45.00"
}
],
It's not a biggy, but it does kind of highlight that the kinks are not all out of the new API yet.
from omnipay-authorizenet.
You're spot-on, the JSON flavour of our XML API can seem "just not quite right". Depending on your timelines our new REST API (Same Authorize.Net API, same organization, XML not going away) will really be a "native JSON" API and should not have these issues. I can send you an email with some more details and timelines.
from omnipay-authorizenet.
Yes, the (estimated) time line for the REST API would be great, with any thoughts on what the API will look like.
from omnipay-authorizenet.
Related Issues (20)
- Add support for retail data to AIMAuthorizeRequest HOT 3
- Add support for track data to AIMAuthorizeRequest HOT 1
- Array to string conversion in CIMAbstractResponse HOT 7
- Add Line Items HOT 2
- Omnipay 3.0 support? HOT 3
- Laravel 5.6 failed HOT 5
- AIMRequest simplexml_load_string chokes HOT 6
- Error on refund
- Error on refund HOT 6
- Add customer info to transaction. HOT 6
- SIM complete purchase response HOT 2
- InvalidArgumentException: Invalid header syntax HOT 1
- Support HMAC SHA-512 hash rather than md5 (urgent) HOT 19
- Invalid paths for AIM query messages HOT 10
- Deprecated API HOT 4
- Need of Full example with all options (optional options also) HOT 1
- Unable to make few partial refunds for transaction
- Show example of passing CreditCard with auth.net HOT 2
- Sale Tax HOT 1
- Declined transactions being passed as successful
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from omnipay-authorizenet.