# Payment Direct API 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 :
ParameterData TypeM/O/CDescription
cardnameVarchar (100)CName on the Credit Card
cardtypeChar(1)CIndicates the card type used.

MasterCard= M
Visa= V
JCB= J
Amex= A

*)mandatory, if merchant post registration for tokenization.
cardnoVarchar (20)CShopper’s Credit Card number

*)mandatory, if merchant post registration for tokenization.
cardcvcChar(4)CCard 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).
expirymonthChar(2)MUse numeric representative of the month i.e.

01 - January
02 - February
…
12 – December

*) mandatory, if merchant post registration for tokenization.
expiryyearChar(4)MFormat of year should be YYYY i.e.2005, 2006 and etc.*) mandatory, if merchant post registration for tokenization.
card_issuer_bank_country_codeVarchar(2)OCountry of the credit card issuing bank.*) mandatory, if merchant post registration for tokenization.
savecardVarchar(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.
paymentoptionIntegerC 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_indVarchar(20)MSpecify the payment indicator to be used for tokenization transaction.
pymt_criteriaVarchar(20)CSpecify the payment criteria to be used, together with the parameter PYMT_IND.
pymt_tokenVarchar(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.

mparam1Varchar(200)MThis field use for direct API tokenization, merchant must be send this params.
**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 :
ParameterData TypeM/O/CDescription
pymt_tokenVarchar (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”

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.faspay.co.id/merchant-integration/api-reference-1/credit-card-transaction/additional-api-integration/api-tokenization/payment-direct-api.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.