¶ Payments
payware platform enables e-commerce websites to accept payment institution facilitated payments. Configure your e-commerce websites 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:
- plain text
- deep link
- barcode generation
- qr code generation
- soundbites
¶ Plain text
payware API provides the transaction ID as a 10-character string (e.g., pw7e4rCToG). Use this for custom integrations or media not directly supported by the API.
¶ Deep link
Clickable mobile application URLs for P2P payments and on-mobile e-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.
¶ 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.
¶ 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, and BLE beacon format), see Transaction Media Formats.
¶ Next steps
E-commerce operators could choose to integrate with payware API or via the available e-commerce plugins. Review E-commerce integration page for more details on how to use API’s and plugins’ specifics for your implementation.
Test your integration before you start accepting live payments:
To make test payments use payware Sandbox environment to:
- Test all the payment methods that you would like to offer.
- Test the following scenarios:
- Error in the POST request – missing or invalid data;
- Send a wrong signature to payware API;
- Check payware API message signature for authenticity;
- The Customer terminates the process on the payware Checkout payment page;
- Customer pays successfully;
- Customer pays successfully, however the merchant’s website does not return HTTP OK to payware API.