Payment Direct API
Last updated
Last updated
Using ‘Payment Direct’ integration, all communication with Faspay e-Payment must be accomplished through secure SSL channel.
Payment direct API request should be sent to the following URL using HTTP POST method:
Development |
---|
Following are the additional parameters you should include in your payment post :
Parameter | Data Type | M/O/C | Description |
---|---|---|---|
Credit Card Payment Response:
Following are the standard parameters that the payment result will pass back as response for credit card payment. For transaction request that has insufficient parameters or incorrect values, it will be rejected by Faspay e-Payment and not stored in the system. Same like standart transaction, tokenization transaction will receive the parameter like TXN_STATUS and others, for tokenization if the transaction success Faspay will send the token on return URL and callback merchant. Additional response param for tokenization :
Parameter | Data Type | M/O/C | Description |
---|---|---|---|
cardname
Varchar (100)
C
Name on the Credit Card
cardtype
Char(1)
C
Indicates the card type used. MasterCard= M Visa= V JCB= J Amex= A *)mandatory, if merchant post registration for tokenization.
cardno
Varchar (20)
C
Shopper’s Credit Card number *)mandatory, if merchant post registration for tokenization.
cardcvc
Char(4)
C
Card Verification Number (Last 3 digits located usually on the back of shopper’s credit card) This field can be optional if the Allow CVC field in Merchant Setting is disabled *)mandatory, if merchant post registration for tokenization. And conditional if merchant use for payment (based on requirement use CVV or by pass CVV on payment process).
expirymonth
Char(2)
M
Use numeric representative of the month i.e. 01 - January 02 - February … 12 – December *) mandatory, if merchant post registration for tokenization.
expiryyear
Char(4)
M
Format of year should be YYYY i.e.2005, 2006 and etc.*) mandatory, if merchant post registration for tokenization.
card_issuer_bank_country_code
Varchar(2)
O
Country of the credit card issuing bank.*) mandatory, if merchant post registration for tokenization.
savecard
Varchar(3)
C
Merchant must be displayed optional for save card data when user fill the card no and etc on registration tokenization. fill savecard = “1”. The “Savecard” parameteronly will be use for registration and payment for add new card. *) mandatory, if merchant post registration and add new card for tokenization.
paymentoption
Integer
C
Payment option used for flag transaction update: Paymentoption = “0” Is for registration or payment without update card transaction. Paymentoption = “1” if you want to add new card for transaction use existing token.
pymt_ind
Varchar(20)
M
Specify the payment indicator to be used for tokenization transaction.
pymt_criteria
Varchar(20)
C
Specify the payment criteria to be used, together with the parameter PYMT_IND.
pymt_token
Varchar(40)
C
This field for data tokens, for transaction registration this filed will be blank (null), but for transaction payment (after registration transaction) fill this field with token from response payment on registration.
Sample token :
“47271385-94F5-410A-9890-09CBB77F2A66”
You can store on your database formapped with a user ID that is registered in the merchant system.
mparam1
Varchar(200)
M
This field use for direct API tokenization, merchant must be send this params.
pymt_token
Varchar (40)
C
Faspay will send the token ID if the transaction success by return URL and Callback merchant.
Sample token :
“47271385-94F5-410A-9890-09CBB77F2A66”