Merchants can use this interface to generate remittance a proof document for successful orders, and the interface will provide the file path for the generated document on SFTP. The merchant can then download the document by connecting to Geoswift SFTP using their credentials(Please contact technical support team to apply for your SFTP account). The proof document for each request will be stored on SFTP for only 30 days and automatically cleared after expiration. Once cleared, the merchant can use this interface again to generate a new proof document when needed.
https://apis.geoswift.com/remittance/voucher/create
Name | Type& Max | Description | Requirement |
---|---|---|---|
merchantId | varchar(9) | The unique identity of the merchant in Geoswift system. Merchant can log in the merchant operation and management system to check | M |
orderRequestId | varchar(50) | The "requestId" previously generated by merchants through "Order Submit Interface"; Remark: only the successful orders with its corresponding "requestId" will be accepted by Geoswift system | M |
partnerId | varchar(9) | The unique identifier of the secondary merchant under the main merchant in the Geoswift system. Note: this parameter can be omitted if the initiating merchant is the main merchant. |
C |
hmac | - | The result of parameter signature,generated by the merchant.For the method of obtaining hmac,please reference to "Geoswift encryption and decryption process specification" | M |
Name | Description |
---|---|
merchantId | The same as the request parameter |
orderRequestId | The "requestId" previously generated by merchants through "Order Submit Interface" |
filePath | The file path of the applied proof documents in Geoswift SFTP |
status | SUCCESS |
ERROR | |
partnerId | The same as the request parameter |
hmac | The result of parameter signature,generated by Geoswift.For the signature verification process,please reference to "Geoswift encryption and decryption process specification" |