¶ In Person Payments
payware platform enables point-of-sale software to take in-person, payment institution mobile applications facilitated payments. Configure your point-of-sale, self-service kiosk, or any other in-person payment solution in the way most convenient for your business. You can customize the payment process depending on your needs. payware has several payment initiation methods:
- plain text
- deep link
- barcode scan/generate (use your POS scanner or screen to initiate bill payment)
- qr code scan/generate (use your POS scanner or screen to initiate bill payment)
- NFC tag scan/emulate (requires NFC enabled hardware)
- soundbites (for TV, recorded or video streaming and radio sales)
¶ Plain text
payware API provides the transaction ID as a 10-character string (e.g., pw7e4rCToG). Use this for custom integrations, manual entry, or API-to-API flows.
¶ Deep link
Clickable mobile application URLs for P2P payments and on-mobile commerce. Link format: https://go.payware.eu/{transactionId}, which redirects to payware://{transactionId} on mobile.
¶ Barcode
payware API generates barcode images with the transaction ID embedded. Available in PNG, SVG, and JPEG formats. For POS scanner hardware integration.
¶ QR code
payware API generates QR code images with the transaction ID embedded as payware://{transactionId}. Available in PNG, SVG, and JPEG formats. When building QR codes client-side, always use the payware:// URI scheme to enable automatic app recognition.
¶ NFC tag
Write an NDEF URI record containing payware://{transactionId} to the NFC tag. This enables automatic app launch when a customer taps the tag with their mobile device.
¶ BLE beacon
Broadcast the transaction ID via BLE Service Data using the payware Service UUID. Enables proximity-based automatic payment detection.
¶ Soundbites
Audio-based payment initiation via acoustic fingerprinting. Enables sales through radio, TV, video streaming, and other audio distribution channels.
For detailed payload format specifications for each media type (including client-side QR construction, NFC tag writing, BLE beacon format), see Transaction Media Formats.
¶ Next steps
Review Merchant/ISV API for more details on how to use API’s specifics for your implementation.