ATHENA-Payments JSON schema

[Gary Moore]

This is a draft of what we're looking for in the JSON that a client would POST to ATHENA-Payments. Comments please.

The file is attached in case the formatting is munged in your system.

----

payment: {
amount:"10.00",
orderId:"order id",
creditCard:{
number:"5105105105105100",
expirationDate:"05/2012",
cardholderName:"Joe Q Ticketbuyer",
cvv:"229"
}
customer:{
firstName:"Joe",
lastName:"Ticketbuyer",
company:"Optional",
phone:"312-555-1234",
fax:"312-555-1235",
email:"j...@example.com"
}
billingAddress:{
firstName:"Suzy",
lastName:"Shipto",
company:"Fractured Atlas",
streetAddress1:"248 W 35th St",
streetAddress2:"FLOOR 10",
streetAddress3:"",
city:"New York",
state:"New York",
postalCode:"10001",
country:"US"
}
shippingAddress:{
firstName:"Suzy",
lastName:"Shipto",
company:"Fractured Atlas",
streetAddress1:"248 W 35th St",
streetAddress2:"FLOOR 10",
streetAddress3:"",
city:"New York",
state:"New York",
postalCode:"10001",
country:"US"
}
}

[Justin Karr]

Gary,

Just documenting something you mentioned to me offline; we are going
to need to consider a token-based authorization model such as the one
used for Braintree or Authorize.net. Would we just have a "token"
field in the "credit card" section of the schema?

Justin

>  payemntsschema.txt
> < 1KViewDownload

[Fintan Donaghy]

I think the authorization token would form part of the http header and would
not be part of the json body sent in a request.

--------------------------------------------------
From: "Justin Karr" <justi...@fracturedatlas.org>
Sent: Friday, October 22, 2010 9:04 PM
To: "ATHENA Tix Developers" <athena-t...@googlegroups.com>
Subject: [athena-tix-devel] Re: ATHENA-Payments JSON schema

> --
> Visit: http://athena.fracturedatlas.org/tix
> Fork: http://github.com/fracturedatlas
> Chat: ##athena on Freenode
>
> You received this email because you are subscribed to the "ATHENA Tix
> Developers" group on Google Groups.
>
> To post, email: athena-t...@googlegroups.com
> To unsubscribe, email: athena-tix-dev...@googlegroups.com
> For more, visit: http://groups.google.com/group/athena-tix-devel?hl=en
>

[Adam Huttler]

Are we actually talking about an authorization token or is this a unique identifier for a stored credit card record? If it's about auth/auth then I agree with Fintan. But if it's about identifying a credit card, then it belongs in the JSON data.

[Gary Moore]

"Token" in this case refers to something the client can use to identify a previously used credit card stored with the processor. Justin, you're right that it needs to be in there. Might get this JSON in then revise to include a tokenized scenario.

Given that "token" is also significant in auth schemes, maybe we need another word for this CC token?

Gary

--
Gary Moore | gary....@fracturedatlas.org | @gsmoore
Fork us on Github: http://github.com/fracturedatlas/
Join us on IRC: ##athena on irc.freenode.net

[Adam Huttler]

"Token" is a pretty generic term in CS, so there's some inevitable ambiguity. Not sure it's a problem, but if it is, maybe just call it a credit card ID?