PSL Wallet - Purchase with Credit Card
Purchase by adding funds to a wallet and then using those funds.
Refer to Section 1 in this document for instructions on submitting an authorization.
In addition the following fields are required to be submitted:
| Variable | Required | Max Size | Value | Notes |
| publisher-name | Mandatory | NA | Gateway account username issued to you. | |
| publisher-password | Mandatory | NA | Remote Client Password - This is different then the password used to login. | |
| walletid | Mandatory | 25 | walletid from when customer signed up for a wallet. Typically this would be the customer’s email address. | |
| passcode | Mandatory | 25 | Password for wallet as chosen by customer; should be alphanumeric. | |
| transflags | Mandatory | NA | load | |
| success-link | Mandatory | NA | URL to send customer to upon successful completion of payment process. | |
| bardcard-link | Mandatory | NA | URL to send customer to upon failure of purchase process. | |
| ipaddress | Mandatory | NA | IP address of customer. | |
| mode | Mandatory | NA | auth |
Notes:
The data returned will contain the name/data pair ‘redirecturl’
If the return response contains this variable, the merchant will be required to redirect the customer to this URL. This can typically done by having the web server ouput the following http header.
Location:$redirecturl ( is a line feed character.)
Once the customer completes the payment process they will be directed to either the badcard-link or success-link URL as applicable.
**We recommend that your success-link script, upon receipt of response string variables, submit a ‘query_trans’ transaction to the payment gateway (see “Query Transaction” in this document) based on the returned orderID and compare the response variable values. This is to validate that the data matches and was not intercepted/manipulated.