Open Dining uses Spreedly to manage credit card data and PCI compliance. All credit card data must be tokenized through Spreedly before it may be used in the Open Dining APIs.
Spreedly provides several methods for creating a card token, such as using a transparent redirect form, direct API call, or JavaScript. It is not necessary to call Spreedly's retain methods, as the Open Dining APIs will handle retaining and purging cards as necessary.
The Spreedly documentation describes adding payment methods. Most third-party applications will use the transparent redirect method if web-based, or the direct API call if not. Please contact Open Dining to get an environment key for Spreedly.
When placing a new order, the card data should first be tokenized through Spreedly, and then the card token data can be sent to Open Dining along with the rest of the order submission. This is very similar to how other in-place tokenization systems work, such as Stripe's Javascript library. The following APIs would be called:
Sometimes a customer just wants to add a new card to their account, without necessarily placing an order. This might occur if they receive a new credit card, or a replacement to an old one. The following APIs would be called:
A customer might want to remove a stored card from their account. This does not require any Spreedly calls.