Consistent functionality across implementation options

Usually, a PSP provides several options to connect to their platform.

For example:

  • plug-ins for popular platforms like WordPress or Prestashop
  • plug-ins/apps for SaaS platforms like Shopify or Lightspeed
  • API access for direct integration with custom built or other platforms

To provide a consistent, quality experience to both end-users and merchants, it is important that the way AfterPay works is mostly identical across all implementation options.

For merchants, some examples are:

  • set a service fee for AfterPay payments
  • cancel or refund an AfterPay payment (if one plug-in supports it, all should support it)
  • configure AfterPay payment methods in multishop systems, following the structure as outligned in this guide

For end-users, this could be:

  • error handling and showing of messages
  • logo usage
  • Dutch language in all messages

These are just examples, the general idea is to have a consistent experience, not matter how a merchant connects with the PSP.