Versions Compared

Version Old Version 14 New Version 15
Changes made by

Juan BARRAZA

Technical Writer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
stylenone

...

This document lists all the PayXpress V4 features available in order to make a an Inter-application (‘app-to-app’) integration between mobile apps installed on the same mobile device.

...

  1. The Merchant Mobile App initiates a transaction by sending a payment request to PayXpress Payment App.

  2. PayXpress Payment App will display screen to Customer in order to present card / inser insert card.

  3. Once the end customer completes the transaction and the POS operation concludes, the POS displays the transaction outcome (Payment accepted or refused).

  4. Optional: PayXpress can offer the posibility to the customer to either retrieve his ticket via QR, or sent send it by Email.

    1. In this case a screen is displayed requesting for this information.

    2. If no ticket is required in a electronic format (QR, Email), then the process to finalize the transaction is realized by PayXpress.

  5. Upon the finalization of the transaction, PayXpress Payment app will export in the Android Intent Reponse the transactions details including the client and merchant ticket.

...

Parameter

Description

Format

Type

Mandatory

transaction_bundle_key_type_print_ticket

Defines which ticket you want to print

0: Merchant & client ticket

1: Client ticket only

2: Merchant ticket only

Integer

Yes

Retrieve

...

Intent’s result

For a transaction

When a transaction is triggered via Intent, it is possible to wait for the transaction result to know the outcome of it.

...

Parameter

Description

Format

Type

Mandatory

status

Outcome of the transaction

0: Accepted

1: Denied

Integer

Yes

transaction

Transaction’s infos

See table below

Transaction

No

tickets

Client & merchant tickets

Json JSON description. See bellow

String

No

...

Parameter

Description

Format

Type

Mandatory

transactionId

Id of the transaction

/

String

Yes

transactionType

Type of the transaction

0: Debit

1: Refund / Credit
2: Cancellation

8: Deferred debit

Integer

Yes

mode

Type of transaction / Payment method

0: Contact

1: Contactless

Integer

Yes

date

Date’s timestamp

171017239300

Long

Yes

reference

Reference of the transaction transamitted transmitted as input

/

String

No

amount

Amount of the transaction

100: 1,00 €

1050: 10,50 €

Integer

Yes

currency

Currency of the transaction

/

String

Yes

aid

Selected AID during the transaction

/

String

No

isDegradedMode

Transaction without network / offline ?

true: Transaction without network / offline

false: Transaction with network / online

Boolean

No

error

Outcome of the transaction

0: Accepted

1: Denied

2: Invalid parameters

3: Transaction already in progress

4: Application in background

5: Error

6: Reference already exists

7: Cancelled

8: Non Not finished

9: Timeout

Yes

maskedPan

Masked PAN of the card

/

String

No

cardLabel

Type of card used

/

String

No

expirationDate

Expiration date of the card

250630

Integer

Yes

amountTips

Amount of the tips (in case the functionality is activated)

100: 1,00 €

1050: 10,50 €

Integer

No

panType

Type of PAN

0: Full PAN

1: Partial PAN

2: Token

Integer

No

numAuthorization

Authorization number if provided by the bank

/

String

No

...

Client and Merchant Tickets are restitued restituted in a JSON Structure.

Each ticket is formatted in ASCII mode and encoded in Base64. This is recommended in order to handle non-alphanumeric data (in alphanumeric), handle carriage returns and small images. .

Currently, it is not possible by PayXpress to export only the client or merchant ticket in the JSON Structure. Both tickets are exported. It is up to the merchant/integrator to filter, based on PayXpress reponse what is the desired ticket that you want to use' response, for the ticket that is desired.

Please find bellow below an example/snipped snippet of Client and Merchant Tickets in JSON Structure:

...

Code Block
{
   "status":1,
   "transaction":{
      "id":"c5a4ba46-e52a-4550-af4e-154d5244ea4e",
      "transactionType":0,
      "mode":0,
      "date":1730907374000,
      "reference":"test",
      "amount":1500,
      "currency":"EUR",
      "aid":"A0000000041010",
      "isDegradedMode":false,
      "maskedPan":"526557XXXXXX2897",
      "cardLabel":"Debito",
      "expirationDate":"300531"
   },
   "tickets":"{"tickets":[{"type":"CLIENT","ticket":"VEFSSkVUQSBCQU5DQVJJQQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIApBMDAwMDAwMDA0MTAxMApEZWJpdG8KIDA2LzExLzI0IC0gMTY6MzY6MTQKUEFZWFBFUlQgRlJBTkNFICA2OSAKTFlPTiAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICAKVkVOVEEgUkVDSEFaQURBCjAwMDE2OTYKMTY4MDgKNTQwMDMyODEwMDAwNDEKWFhYWFhYWFhYWFhYMjg5NwoxNjMgMDAxIDAwMDAxMiAgMDEgIEMgIEAKTlVNRVJPIEFVVE9SSVpBQ0nTTjogClJFRi4gOiAyTURTSU5FUUxPMTEwNiAgbjVnYTNVS2ZRTVM4bzdpN3hybW9ZdwpJTVBPUlRFCjE1LDAwoEVVUgpSRUNJQk8gUEFSQSBFTCBDTElFTlRFCkEgQ09OU0VSVkFSCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCg=="},{"type":"MERCHANT","ticket":"Q0FSVEUgQkFOQ0FJUkUKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKQTAwMDAwMDAwNDEwMTAKRGViaXRvCk9OIDA2LzExLzI0IEFUIDE2OjM2OjE0ClBBWVhQRVJUIEZSQU5DRSAgNjkgCkxZT04gICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAgCkRFQklUIERFQ0xJTkVECk1PVElGIFROQSA6IDIxIDEyCjAwMDE2OTYKMTY4MDgKNTQwMDMyODEwMDAwNDEKMjAxMApYWFhYWFhYWFhYWFgyODk3CmVuZCAzMS8wNS8zMAoxNjMgMDAxIDAwMDAxMiAgMDEgIEMgIEAKQVVUSE8gTlVNIDogClJFRi4gOiAyTURTSU5FUUxPMTEwNiAgbjVnYTNVS2ZRTVM4bzdpN3hybW9ZdwpBTU9VTlQKMTUsMDCgRVVSCk1FUkNIQU5UIFRJQ0tFVApUTyBCRSBLRVBUCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCg=="}]}"
}

For a ticket print

...

on the POS

When the instruction to print a ticket is triggered via Intent, it is possible to wait for the result to know the outcome of it.

...