payware platform enables payment institutions to provide to their customers mobile facilitated payments. Configure your payment institution application in the way most convenient for your business model. You can customize the payment process depending on your needs. payware has several payment initiation methods:
payware API plain text option provides you with transaction ID in 10 characters long string format. You can use that to enable payment initiation process which is not directly supported by the payware API (NFC tags).
Transaction ID example: pw7e4rCToG
Traditional deep links can route users to app content as long as the app is already installed when the link is opened. This means traditional deep links don’t work if the user doesn’t have the app, and will show either an error or a fallback page.
Deep links are typically designated for:
P2P payments initiated via messaging service.
Ecommerce payments initiated on-mobile-only environment.
Deep links allow partners to publish clickable mobile application URLs.
Deep link transaction ID example: pw7e4rCToG
Link format: https://url.payware.eu/{transactionId}
.
On click response: payware://{transactionId}
payware API Barcode option provides you with transaction ID embedded in barcode image. The image could be delivered in PNG, SVG and JPEG formats.
Barcode transaction ID example: pw7e4rCToG
payware API QR code option provides you with transaction ID embedded in qr code image. The image could be delivered in PNG, SVG and JPEG formats.
Barcode transaction ID example: pw7e4rCToG
If you want to scan/emulate NFC tags use plain text transaction IDs in your specific implementation.
Registering existing audio enables payment initiations and direct sales and delivery business models via radio, TV or other audio advertisement distribution channels.
Real time soundbites based advertisement efficiency data is available for partners’ analysis.
Follow the Payment institution API for more details on how to use all API’s specifics for your implementation.