Update Card
Post Data
| Action | Description |
|---|---|
When | Merchant want to make data card transaction changes for an existing member |
What To Do | Post data to Faspay, Merchant will get response and please keep the member_id from the response’s. |
URL Endpoint
| Integration Method | URL - Development | URL - Production |
|---|---|---|
Merchant Window API | ||
Merchant Direct API |
Request parameter :
| Parameter | Data Type | M/O/C | Description |
|---|---|---|---|
recurring_type | Varchar (1) | M | For Update member, please fill this parameters with = 2 |
merchant_id | Numeric(5) | M | Merchant ID given by Faspay |
member_id | Varchar(50) | M | Merchant’s Member ID for recurring (generated by merchant) |
member_name | Varchar(50) | M | Merchant’s Member Name |
member_email | Varchar(50) | M | Merchant's Member Email |
member_email_notif | Varchar(1) | M | Merchant's Member Email Notification |
process_date | Varchar | M | Process date, this parameters used for date of transaction and date of retry recurring if there is a failed recurring. Sample : process_date = "12,15,20,25,01,05,10". (Max 9 date)
12 is a date for register new recurring transaction date.
15,20,25,01,05,10 is a date for retry recurring if any failed recurring to this member. |
recurring_amount | Numeric(12) | M | Recurring Amount is used for transaction amount on recurring process. |
recurring_start_date | Date(10) | M | Recurring Start Time (must be same day with the transaction date) |
recurring_end_date | Date(10) | M | Recurring End Time |
|
|
|
|
recurring_period | Varchar(1) | M | Recurring Period : M = Monthly Y = Yearly |
recurring_perriod_at | Numeric(1) | M | Repetition of Recurring Period, sample case : if user fill recurring_period with M (monthly), recurring_perriod_at is used for repetition of deduction by period. Sample : - recurring_period : M - recurring_perriod_at : 1 so, recurring will process by system per months, if fill with 3, recurring will process per 3 months.
|
recurring_accumulate | Varchar(1) | M | Recurring Accumulate : t |
recurring_accumulate_at | Numeric(1) | M | Repetition of Recurring Accumulate in Days |
recurring_status | Varchar(1) | M | Recurring Status : t |
recurring_signature | Varchar(10) | M | Recurring Signature : sha5(md5(user_id+password+member_id)) |
Response
| Action | Description |
|---|---|
When | Receiving |
What To Do | Post data to Faspay, merchant will get a response from Faspay and please keep the member_id from the responses. |
| Parameter | Data Type | M/O/C | Description |
|---|---|---|---|
recurring_type* | Varchar(1) | M | Indicates the recurring type of transaction,1 for register new member. |
member_name | Varchar(50) | M | Merchant’s Member Name |
member_email | Varchar(50) | M | Merchant's Member Email |
member_email_notif | Varchar(50) | M | Merchant's Member Email Notification |
process_date | Varchar | M | Process date, this parameters used for date of transaction and date of retry recurring if there is a failed recurring. Sample : process_date = "12,15,20,25,01,05,10". (Max 9 date)
12 is a date for register new recurring transaction date.
15,20,25,01,05,10 is a date for retry recurring if any failed recurring to this member. |
reccuring_amount | Numeric(12) | M | Recurring Amount is used for transaction amount on recurring process. |
recurring_start_date | Date(10) | M | Recurring Start Time (must be same day with the transaction date) |
recurring_end_date | Date(10) | M | Recurring End Time |
recurring_period | Varchar(1) | M | Recurring Period : M = Monthly Y = Yearly |
recurring_period_at | Numeric(1) | M | Repetition of Recurring Period, sample case : if user fill recurring_period with M (monthly), recurring_perriod_at is used for repetition of deduction by period. Sample : - recurring_period : M - recurring_perriod_at : 1 so, recurring will process by system per months, if fill with 3, recurring will process per 3 months. |
recurring_accumulate_at | Numeric(1) | M | Repetition of Recurring Accumulate in Days |
recurring_status | Varchar(1) | M | 1 for active, 0 for inactive |
payment_method* | Varchar(1) | C | Indicates the payment mode used to process this transaction.In the event of error,this field may be empty. Refer to Appendix E for Available Payment Methods |
merchantid | Varchar (30) | M | Your Faspay Credit card MerchantID |
merchant_tranid | Varchar(100) | M | Merchant’sown assigned transaction id as passed in from The request. |
err_code* | Varchar(10) | M | Error Code returns from Faspay Credit card. If transaction is successful,this value will be 0. Any other value than 0 will indicate that the transaction is not successful. |
err_desc | Varchar(250) | M | Error description from Faspay Credit card based on the ERR_CODE. |
usr_code | Varchar(4) | C | User Code returns from Faspay Credit card.A user code Will be used to indicate the appropriate action to be taken by shopper according to different bank response code obtained. In the case of pending status,this value is will an empty value |
usr_msg* | Varchar(200) | C | User Message returns from Faspay Credit card.A user message will be used to indicate the appropriate action to be takenby shopperaccordingto different bankresponsecode obtained. Inthecase of pending status,this value is will an empty value |
txn_status* | Varchar(3) | M | Transaction status from Faspay Credit card.
A–Authorized S –Sales F–Notapproved E –Error B –Blocked RC –Reconfirm N –Pending I–Incomplete
This value must be stored and it’s the indication whether the transaction is successful,declined or error. |
custname | Varchar(120) | M | Shopper’s name as passed in from the request. |
description | Varchar(100) | O | Transactiondescriptionaspassedin fromtherequest. |
currencycode* | Varchar(3) | M | Currency code as passed in from the request. Refer to Appendix for SupportedCurrencies |
amount | Numeric(10) | M | Transaction amount as passed in fromtherequest. |
signature | Varchar(40) | M | Transaction signature of response for data integrity checking.RefertoChapter 5TransactionSignaturefor details. |
transactionid | Integer | M | Faspay Credit card assigned transaction id if the Transaction was stored. This value must be stored and used as reference value to retrieve the transaction from Faspay Credit card.
In the event that if the request parameters are invalid, the transaction is rejected and not stored, this value will be 0. |
trandate | Varchar (19) | C | Transaction date of when transaction is submitted to Faspay Credit card. Date formatin ‘DD-MM-YYYYhh:mm:ss’ e.g.24-05-200608:24:23 In the event of error, this field may be empty. |
transactiontype | Varchar(2) | C | Indicate the transaction type used for this transaction. In the event of error, this field maybe empty. |
is_blacklisted | Varchar(5) | C | Indicate whether the transaction is blacklisted. Value is ‘Yes’ or ‘No’ In the event of error, this field maybe empty. |
fraudrisklevel | Integer | C | Indicate fraud risklevel. Valueas follow: -1 : Error or notinused. 0–Very lowrisk 1– Lowrisk 2–Medium risk 3–High risk 4–Very high risk
In the event of error, this field maybe empty. |
fraudriskscore | Numeric | C | Fraud risk score in two decimal values. In the event of error, this field maybe empty. |
exceed_high_risk | Varchar(3) | C | Indicate whether the transaction fraud score exceed the threshold value set for highrisk in merchant setting. Possible value are:
|
mparam1 | Varchar(50) | O | Additional parameter as what is passed in request. This value is not stored by Faspay Credit card. |
mparam2 | Varchar(50) | O | Additional parameter as what is passed in request. This value is not stored by Faspay Credit card. |
acquirer_bank | Varchar(30) | O | Your Faspay Credit card Acquirer ID |
member_id | Varchar(50) | M | Merchant’s Member ID for recurring (generated by merchant) |
Last updated