AFCheckKeySDK Test Steps

Getting Started

Additional documentation on how to implement the AFCheckKeySDK methods can be found at: Argofire Sdk Documentation

Click here to run in test environment

1. Create client session ID:

Important: Implement this method only on Server-side

CreateClientSessionID method should be called from Server-side, so that ClientSessionID can be returned or embeded in the page returned to browser in order to process next step. This below test is implemented on the client-side only for demo/testing purposes.

+ Server-side implementation

Endpoint https://secure.ftipgw.com/admin/ws/recurring.asmx/GetClientSessionID ‌

Method POST

content-type‌ text/xml; charset=utf-8 or application/x-www-form-urlencoded

Headers‌ NO-HEADERS‌

Params‌‌ Username Password Vendor

Payload‌‌ NO-PAYLOAD‌‌

Params‌‌‌

Attribute	Type	Required	Description
Username	String	Yes	The username of the admin user.
Password	String	Yes	The password of the admin user.
Vendor	Int	Yes	The numerical Vendor/Merchant key.

Possible‌ ‌Responses‌ ‌‌

HttpStatusCode‌	Message‌	Reason‌
200‌	Success‌	Client Session ID is created successfully.
400‌‌	Failed‌‌	Invalid request.
404‌	Failed‌	Endpoint‌ ‌address‌ ‌is‌ ‌incorrect‌ ‌or‌ ‌bad‌

If the request is successful you should see the Client Session Id code in the last text area, else you will see a popup with error message

Username Merchant assigned Username.

Password Enter Password.

Vendor

Received Client Session ID:

2. Get Check Token

+ Get Check Token

GetCheckToken request should be implemented only on client-side and should have the following hosted fields on browser.
If the request is successful you should see the CheckKeyInfo in the last text field, else you will see a popup with error message

Client Session ID Set Client Session Id received in GetClientSessionID request.

Account Number

Routing Number

Name On Account

Check Type

Account Type

Street

Zip

First Name

Last Name

Received CheckInfoKey:

3. Process Check

+ Process Check

Important: Implement this method only on Server-side

ProcessCheck request should be called from Server-side. This below test is implemented on the client-side only for demo/testing purposes.

+ Server-side implementation

Endpoint https://secure.ftipgw.com/smartpayments/transact.asmx/ProcessCheck

Method POST

content-type‌ text/xml; charset=utf-8 or application/x-www-form-urlencoded

Headers‌ NO-HEADERS‌

Params‌‌ Username Password TransType CheckNum Amount DL SS DOB StateCode CheckType ExtData

Payload‌‌ NO-PAYLOAD‌‌

Params‌‌‌

Attribute	Type	Required	Description
Username	String	Yes	The username of the admin user.
Password	String	Yes	The password of the admin user.
TransType	String	Yes	Type of transaction.
CheckNum	String	Yes	Check number uniquely identifies each individual check.
Amount	String	Yes	Enter amount.
DL	String	No	The check holder's driver's license number.
SS	String	No	The check holder's Social Security Number.
DOB	String	No	The check holder's date of birth.
StateCode	String	No	The check holder's 2 character state code.
CheckType	String	No	Check Type.
ExtData	String	No	ExtData should include CheckInfoKey. For example: <Check_Info_Key>618704</Check_Info_Key>

Possible‌ ‌Responses‌ ‌‌

HttpStatusCode‌	Message‌	Reason‌
200‌	Success‌	Successfully processed the transaction.
400‌‌	Failed‌‌	Invalid request.
404‌	Failed‌	Endpoint‌ ‌address‌ ‌is‌ ‌incorrect‌ ‌or‌ ‌bad‌

If the request is successful you should see the PNRef in the last text field, else you would see a alert of error

Username Merchant assigned Username.

Password Enter Password.

TransType

Check Num

Amount

Driver License Number

Social Security Number

Date of Birth

State Code

Check Type

ExtData

Received PNRef: