BENEFICIARY: Perform Name Change
RSP can use this method to request amendment on beneficiary name. Amendment request will be based on the transaction status and corridors. For cash pickup transaction, only transaction with the payout status “In Process” or “Unclaim” is able to be amend. For banks transactions, the amendment is strictly based on the banks and country regulations.
Definition:
PUT v1/payments/transfers/{GTN}/requests/{transID}/change-name
Sample Request:
curl -v -X PUT http://staging-gloremit.tranglo.com:2014/v1/payments/transfers/G3717307424573/requests/2017110201/change-name \
-H "Content-Type: application/json \
-H "Authorization: GLOREMIT <UID>:<PWD>:<rspSign>" \
-d '{
"beneFirstName": "Oppo",
"beneLastName": "Frank"
}'
Request Description
Parameter Name | Required | Min/Max Length | Type | Remark |
UID | M | 5/50 | Alphanumeric | Username for validation. |
PWD | M | 5/50 | Alphanumeric | Password for validation, 3DES encrypted. |
rspSign | M | 32/50 | Alphanumeric | Digital signature of RSP. (Please refer to Digital signature) |
transID | C | 3/6 | Alphanumeric | Unique transaction ID used by RSP in Change Name method. |
trangloTransactionId | M | 14/14 | Alphanumeric | Transaction GTN number. (14 characters) |
beneFirstName | M | 1/100 | Alphanumeric | New beneficiary first name. |
beneLastName | M | 1/100 | Alphanumeric | New beneficiary last name. |
Response Description
Sample Response:
{ "TrxStatus":"946", "ChangeId":"null", "transID":"2017110201", "Description":"Duplicate Request" }
Parameter Name | Required | Type | Remark |
TrxStatus | M | Numeric | Transaction status response code. (Please refer to Transaction status) |
ChangeID | M | Alphanumeric | 14-character change name ID. |
transID | M | Alphanumeric | Unique Transaction ID from RSP. |
Description | M | Alphanumeric | Transaction description or advice. |
M= Mandatory, C= Conditional, O= Optional