Create, send, and follow payment requests.

 

 

What is a payment request?

A payment request is a link to a unique web page in which transaction details have already been pre-filled and it is ready to be paid.

  • The link can be offered as a URL, as a button or as a banner.
  • This link can be sent in a message or made available somewhere else (PDF, website, app etc.). 
  • Email and SMS messages can be designed and sent with Serrala Alivate RTP. For other types of messages and channels you can easily take care of the API integration yourself.
  • The transaction is a unique combination of data including the payment amount, reference, due date, description, and beneficiary details.
  • The recipient of a payment request can pay with one of many predefined online payment methods (iDEAL, Sofort, PayPal, credit card, etc.).
  • Once paid or expired, a payment request can no longer be paid to avoid duplicate payments and confusion.

Customizations. You have the option to create customizations and add specific features specially designed to fit your specific needs such as authorizations, partial payments, premiers, PDF specifications, corporate identity, languages, currencies, etc.

Applications. Organizations use our payment requests for invoices, reminders, payment arrangements, reservations, authorizations, online purchases and much more.  

Can't wait to get started?

Take me to Github.

Applications and integrations

Developers can deploy Serrala Alivate RTP in multiple ways:

  • Batch processing: Periodically create and send out many (thousands) payment requests - and possibly simultaneously make copies available in the customer portal.
  • On-the-fly: Create and offer payment requests straight from within your back-office system.

The required data for payment requests must usually come from a source system such as an ERP, CRM, accounting, or credit management package. You can decide to integrate payment requests straight from within your website, app, or both. There are many possible configurations and usually done with any of the following options:

  • Rest API: Check our online documentation
  • SOAP API: We have a detailed integration guide for easy implementation
  • Managed Account: You submit batch files (such as XML or CSV) via a secure SFTP connection after which Serrala processes and sends out the payment requests.

In all cases it is possible to recover the status of each message and every payment (real time or otherwise) which offers great added value in business processes.