WebioPay - Conversational Payments

WebioPay - Conversational Payments

Designed to optimise customer payments, Webio’s ‘Conversational Payments’ skill brings instant live payment requests and processing into customer conversations making it easier for agents to send customer payment links as they interact with customers via messaging.  Webio bots can be triggered by API, web app uploads or by agents from within the conversation screen.

Connecting your payment service provider (PSP) to your Webio organisation.

To get started with Conversational Payments, add your PSP details within the organisation screen of Webio.  

1) Click on Organisation, scroll down and select ADD GATEWAY

2) Select your Payment Service Provider (PSP) from the drop-down.  If your PSP isn't listed please contact support@webio.com.

3) Fill in the details requested. Each PSP has different requirements; typically this will be a username, password and a key. 

Stripe you will need your private key.
Cybersource you will need your username and transaction key
Barclays ePDQ Extra Plus you will need your pspid, user ID and password
Data Cash you will need your client and your password.

Gateway Type
Once you select your PSP the required information will be displayed.  Click Create Gateway.  You will now see your new PSP listed.  

Please remember at this point the connection hasn't been verified, this will happen when you send your first test through.

Creating payment steps within bots.

Payments are a step type within your Webio bot.  This means you can add them into your bot and set the routes to deliver the conversation journey you want.  

1) Within your bot click create step and then set the Type to Payment Step.

2) Under Gateway select the payment service provider you wish to use.  If it isn't appearing in the list check above for how to add a PSP to your organisation.

3) Fill in the remaining information:

Description: this field will be passed across onto your PSP reporting.  You can include dynamic values here by providing the #fieldname#.
Company Name: This will appear on the payment i-frame.
Payment Widget Description: This will appear on the payment i-frame.
Currency: Select either Sterling or Euro
Payment value: this is the name of the field containing the amount to be processed.  This can either be provided in the upload or provided by the customer in a listening step during the conversation. These values are assumed to be currency fields so shouldn't contain symbols (£,€ or other text).  The system treats anything before the decimal point as pounds/euros and anything after as pence/cent.
On success: sets the route your bot will follow if the payment is successful.
On failure: sets the route your bot will follow if the payment is unsuccessful.

4) On this step your bot will send a payment link, that will open a secure i-frame when clicked. 

Once the information is completed and the Pay Now button clicked, the payment is handled between our Payment Gateway Spreedly and your PSP and the bot will continue based on whether the outcome is successful or not.

Want to include your customer reference with the payment request to appear in your PSP reporting?  Include the dynamic field that contains the reference number with the description field, using #fieldname# and this will flow through with the transaction.

    • Related Articles

    • Adding payment gateways to your Organisation

      Webio now provides Spreedly integration, allowing you to use your bots to accept payments over 120 different payment gateways.  The sensitive card data is tokenised and stored by Spreedly, never touching the Webio platform, allowing you peace of mind ...
    • Typeform Conversations - Reopen on submission

      When a Conversational Form is submitted to a conversation that has already been closed, the conversation will now reopen. Using the Webio integration with Typeform, you can add the power of conversational forms to your automated and agent ...
    • Webio - Information Security and Data Protection

      Webio incorporates information security and data protection principles into everything we do.   Below are some of the ways in which we put this into practice. Disaster Recovery and Business Continuity - Webio's disaster recovery plan is reviewed ...
    • Step types

      Bots are built as a series of steps.  When you create a new step you need to choose what type of step it is.  Below is a brief explanation of what each type does. Information Information steps send the message you have set and then move on to the ...
    • Integrating a Dialogflow agent

      Dialogflow agents use natural language understanding to return intents.  When used as part of your Webio Conversational Middleware solution they allow your bots to manage conversations with natural fluency, allowing a conversational tone that will ...