Skip to content

Commit e922769

Browse files
committed
Updating README file
1 parent 05609e9 commit e922769

1 file changed

Lines changed: 25 additions & 1 deletion

File tree

README.md

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,25 @@
1-
# cybersource-flex-samples
1+
## Flex Token API
2+
3+
### Introduction
4+
5+
Storing your customer’s card data can dramatically increase your repeat-custom conversion rate, but can also add additional risk and PCI DSS overhead. This can be mitigated by tokenizing card data. CyberSource will store your customer’s card data, replacing it with a token that can only be used by you.
6+
7+
Flex Token API, currently in private beta, is our most secure method for Tokenizing card data. Your customer’s card number is encrypted on their own device, for example inside a browser or native app, and sent directly to CyberSource. This means card data bypasses your systems altogether, typically qualifying e-commerce only merchants for [SAQ A-EP](https://www.pcisecuritystandards.org/documents/Understanding_SAQs_PCI_DSS_v3.pdf).
8+
9+
On-device encryption helps to protect your customers from attacks on network middleware such as app accelerators, DLPs, CDNs, and malicious hotspots.
10+
11+
The token can be used in lieu of actual card data in server-side requests for other CyberSource services, such as [Payer Authentication](http://apps.cybersource.com/library/documentation/dev_guides/Payer_Authentication_SO_API/Payer_Authentication_SO_API.pdf), [Decision Manager](https://www.cybersource.com/products/fraud_management/), [Tax Services](http://apps.cybersource.com/library/documentation/dev_guides/Tax_SO_API/Tax_SO_API.pdf), and [Card Payments](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SO_API/Credit_Cards_SO_API.pdf).
12+
13+
The Flex Token API is a JSON based RESTful service, consisting of two resources: **keys** and **tokens**.
14+
15+
#### Keys
16+
17+
Create a public key to encrypt the card data on your customer's device (a browser or a native app). This is an authenticated request when rendering your payment form or control.
18+
19+
#### Tokens
20+
21+
Create a token using the encrypted card data. This is an unauthenticated request from your customer's device. The endpoint supports [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing), so AJAX requests are supported from browser based implementations.
22+
23+
### Examples
24+
25+
These repositories consist of two example web implementations, in [Java](java) and [C#](dotnet). They consist of a basic server that requests the keys and serves a front end that collects, encrypts and transmits the card data directly to CyberSource. Please ensure you read [our license](LICENSE.md) prior to making use of the provided code.

0 commit comments

Comments
 (0)