Luisa Osorio

PAYU Swipe Application Updates and actualization Second updates Luisa Osorio 06/03/2013 Update 1: Additional field for reference code For Android and IOS The application is currently following these guides for the “reference code” variable: Application guidelines for request: Primary node transaction.order.accountId: The app must use the variable “webUserResponse.webUser.accountsId.int” obtained from the authentication API transaction.order.referenceCode: The app must generate a consecutive sequence of numbers for each transaction and send the consecutive number in this variable. transaction.order.description: This must come from the input field “¿Qué estas vendiendo?” on screen 2 of the application transaction.order.airlineCode: Ignore transaction.order.language: For this please use “es” for Spanish So the application is now generating and sending this variable automatically as a consecutive number. Ex: “PUS-”. Change: We will need to add a field called “Referencia de venta (Opcional)” on the home screen “Información de venta” in order for the seller to be able to provide a reference number if needed. The new field “Referencia de venta (Opcional)” will be optional, so if the field is left empty the applications must automatically send the variable “reference code” with the consecutive sequence (ex: PUS-) that it is sending today. Additionally, the application must now send another variable called “Extra 1” with the same value it is sending now as the variable “reference code”. So in case a seller leaves the “Referencia de venta (Opcional)” field empty, the application would have to send the value “PUS-” for both the variable “reference code” and the variable “Extra 1”. If a seller enters a different value on the new field “Referencia de venta (Opcional)”, the application will have to send the seller’s input as the value for the variable “reference code” and send the value it was generating before (ex: PUS-” ) only on the “Extra 1” field. The method that must be used to send the “Extra 1” variables is the same as the method used for the variable “Installements” It must be an extraParameter: transaction.extraParameters transaction.extraParameters.entry transaction.extraParameters.entry.string: Use “EXTRA_1” transaction.extraParameters.entry.string: Ex: PUS- New field format: Related screen: Screen 2: Sale information- “Información de venta” Field name: Reference code Text: Referencia de venta Input space: Example for “Reference code” Text: Ej: Zapatos2345 Must be fainted as example and disappear when the user enters the corresponding text. Format: English alphabet letters, special characters and numbers Help button: Text: Si quieres tener una número de referencia para tu venta puedes ingresarlo en este espacio. Ej: Zapatos2345 Screen shot Update 2: Update SDK version 3.0 For Android and IOS The application is integrated with the “Shuttle” device from IDTech though and SDK V2.10 to capture the credit card’s information. IDTech has release a v3.0 of the SDK which now support more phone models and especially some models that are sold in Colombia. The new SDK version is available through: http://sdk.idtechproducts.com/sdk_info.asp The download code for our company is: 393FFCC6 Change: We must update the SDK integration to V 3.0