Scribd
Upload
373 views9 pages

Clover Payment

The document describes the process for integrating credit card payments into an application using Clover. [1] Information is collected on a payment form and sent to Clover to generate a token. [2] The token is then used to make a charge request to Clover's API to process the payment. [3] Clover returns a response with payment details that are stored and used to confirm the transaction.

Uploaded by

Anodyne test1
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
373 views9 pages

Clover Payment

The document describes the process for integrating credit card payments into an application using Clover. [1] Information is collected on a payment form and sent to Clover to generate a token. [2] The token is then used to make a charge request to Clover's API to process the payment. [3] Clover returns a response with payment details that are stored and used to confirm the transaction.

Uploaded by

Anodyne test1
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 9

Clover Payment

Clover merchant portal:

We are having two integration methods.

1. Iframe Token

2. Rest API Token

Iframe integration & Credit card payment

The following diagram shows the basic flow of required information and the software
components that interact to complete a charge request. You add a form to your webpage
and insert the Clover-hosted elements to collect and process the user's card information.
This information is used to create the card token used by the server to complete the
payment. This charge operation must be a server-to-server call. Clover software is shown in
green, and your app's software is shown in blue.
1. Direct the user to the iframe in a manner consistent with your application's user flow.
2. Wait for the user to enter and submit their card information.
The server returns the tokenized card as a  source.
3. Create a charge request with the source and a specific amount in cents.
4. Send the charge request to the SCL charge endpoint ( POST /v1/charges).
The card is charged for the specified  amount.
1. SDK integration :

Added SDK.js in Anodyne application with clover support files.

<script src="https://cdn.polyfill.io/v3/polyfill.min.js"></script>
<script src="https://checkout.sandbox.dev.clover.com/sdk.js"></script>
2. Key Token integration :

We are using following keys for CC transaction.

a. Iframe public key

b. Rest API private key

above keys are configurable in Anodyne practice setup with merchant details.

3. Generate Order number:

Creating order number as Anodyne payment reference and storing in database.

4. Charge Request form :


Creating payment details screen in Anodyne. It has Card number, expiry date , CVV and Zip core
are mandatory filed to generate CTOKEN.

5. CTOKEN Request :

Send card information along with Order number(which was created by Anodyne app), paid
amount and API key to Clover server. Clover server has validate card information and API keys.

6. CTOEKN Response :

Clover server has send CTOKEN to client after validation and storage.

{
token : clv_1TSTSNcKAUqMaP1m2P22vMwt
}

Staring token information and payment information in Anodyne database.


7. Create charge:

We are calling endpoint /v1/charges using RestAPI.


Request will include paid amount, ordernumber, CTOEKN.
Authentication method : Oauth2
Sample :
{
"ecomind": "ecom",
"amount": 2300, --- Clover playing with cents
"currency": "usd",
"source": "clv_1TSTSLb1dGtebUWnMTtZfXY4",
"external_reference_id": "1234"
}

8. Charge Response:

After COTKEN validation, Clover server has send charge response with transaction
details.

Sample :

"id" : "ZDXVXNAX4J0XE",

"amount" : 11,

"amount_refunded" : 0,

"currency" : "usd",

"created" : 1638369310295,

"captured" : true,

"ref_num" : "133500500060",

"auth_code" : "OK8632",

"outcome" : {

"network_status" : "approved_by_network",
"type" : "authorized"

},

"paid" : true,

"status" : "succeeded",

"source" : {

"id" : "clv_1TSTSNcKAUqMaP1m2P22vMwt",

"address_line1_check" : "unavailable",

"address_zip" : "75202",

"address_zip_check" : "pass",

"brand" : "DISCOVER",

"cvc_check" : "pass",

"exp_month" : "06",

"exp_year" : "2023",

"first6" : "601136",

"last4" : "6668"

},

"external_reference_id" : "123456",

"ecomind" : "ecom"

Do you want to store entire response?


9. Payment receipt:

10. Validation and deduction:

Validating Clover response and doing detection process for validate status.

11. Payment receipt email

Generating payment receipt using succuss response.

Need to clarify Error response model?

Ordernumber and Ctoken were missing in Error modal.


Clover Configuration
1. Add Clover in Practice under Superadmin

2. Merchant information configuration.

3. Configuration integration with Anodyne API calls.

Clover testing
Have to test all payment gateways and payment features.

You might also like