Get_PaymentValidation - Tranglo

Get_PaymentValidation

Corporate Customers can use this method to perform payment validations to ensure payment inputs are securely verified.

Definition

POST/api/payments/payment-validation

Sample Request

curl -X POST
-H "Authorization: BEARER "
-d '{
"Reference_ID": "RT123123123213",
"Account_ID": 214580100000278,
"Payout_Information": {
"Payout_Country": "PH",
"Payout_Currency": "PHP",
"Payout_Amount": 1000.00,
"Purpose_Code": 1,
"Trxn_Type": 1,
"Fund_Source": 2,
"FR_Key": "FR_KEY_FOR_FUTURE_USE",
"Remark": "Payment for services"
},
"Beneficiary": {
"Beneficiary_Type": "I",
"Full_Name": "Jane Smith",
"Nationality": "PH",
"Birth_Date": "02/02/1992",
"Identification":
{
"ID_Type": 3,
"ID_No": "ID987654321"
},
"Relationship": 1,
"Bank_Details": {
"Issuer_Code": "520",
"Account_Type": 1,
"Account_Number": "012345678901",
"Bank_City": "Manila",
"Bank_Province": "NCR",
"Bank_Postcode": "1000",
"Bank_Branch_Name": "Main Branch",
"Bank_Branch_Code": "AFBQMYKL"
},
"Address": {
"Address": "456 Another St",
"Province": "NCR",
"Regency": "Manila",
"City": "Manila",
"Postcode": "1000"
},
"Contact_Person": {
"Contact_No": "639123456789",
"Email": "jane.smith@domain.com"
}
}
}

Request Description

Parameter NameRequiredMin/Max LengthTypeRemark
AuthorizationMBearer <jwt-token>StringBearer <jwt-token>
• The JWT token used for authentication must be passed in the Authorization header prefixed with Bearer.
Reference_IDM6/48StringUnique TB Corporate Customers reference ID.
Account_IDM15/15NumericTB Corporate Customer's Account ID/ Wallet Account ID.
Payout_CountryM2/2CharAccept ISO 3166-1 Alpha-2 ONLY
Payout_CurrencyM3/3CharAccept ISO 4217
Payout_AmountM1/16NumericPayout's Total Amount.
Purpose_CodeM5/15StringPurpose of the transaction.
Trxn_TypeM1/2NumericTransaction Type/Transaction Channel.
Fund_SourceM1/2NumericSender's source of fund.
RemarkO1/100StringPayment Remark.
FR_KeyO32/32StringFR key for future use.
Beneficiary_TypeM1/1NumericEither (2) Corporate or (1) Individual.
Full_NameM6/200String
NationalityM2/2CharBeneficiary's Nationality. - Accept ISO 3166-1 Alpha-2 ONLY
Birth_DateO8/8Date (DD/MM/YYYY)Beneficiary's Birth date.
ID_TypeM1/1NumericBeneficiary's Identification Type.
ID_NoC8/50StringBeneficiary's Identification Number.
RelationshipM1/2NumericBeneficiary Relationship.
Issuer_CodeM3/16StringBeneficiary Account's Issuer Code.
Account_TypeO1/1NumericBeneficiary's bank account type.
(1) - Saving
(2) - Checking
(3) - Current
(4) - Others
Account_NumberO1/30StringBeneficiary's account number.
Bank_CityO1/50StringBeneficiary's bank city.
Bank_ProvinceO1/50StringBeneficiary's bank province.
Bank_PostcodeO1/10StringBeneficiary's bank postcode.
Bank_Branch_NameO1/100StringBeneficiary's bank branch name.
Bank_Branch_CodeO1/50StringBeneficiary's bank branch code.
AddressO2/50StringBeneficiary's full address.
ProvinceO1/50StringBeneficiary's address province.
RegencyO1/50StringBeneficiary's address regency city.
CityO2/30StringBeneficiary's resident city.
PostcodeO1/50StringBeneficiary's address postcode.
Contact_NoO8/30NumericBeneficiary's contact number.
EmailO5/50StringBeneficiary's email address.

Sample Response:

HTTP 200 OK
{
"Payment_ID": "B1252600000001",
"Reference_ID": "RT123123123213",
"Payment_Status": {
"Status": "ACCEPTED",
"Status_Code": 965,
"Sub_Status_Desc": ""
},
"LastBal": 1000.00,
"CurrRate": 1.05
}

Response Description

ParameterData TypeRequiredDescription
Payment_IDStringMPayment ID generated by Tranglo.
Reference_IDStringMUnique Reference ID from Corporate Customer.
StatusStringMTransaction Status.
Status_CodeNumericMTransaction Status Code.
Sub_Status_DescStringMDescription of transaction status.
* Note: For a FAILED status, the system will return all the reasons for the transaction failure.
LastBalNumericMThe latest balance of Corporate Customer wallet.
CurrRateNumericMThe transaction currency rate.

M = Mandatory, C = Conditional, O = Optional