PayShap Operator Guide
You have implemented Electrum’s PayShap solution. This operator guide will show you what you can expect from your PayShap service, and potential errors that can occur. It will provide an overview of the tools that you can use to monitor your service, and help you to investigate and solve errors that occur during transaction processing.
This guide covers the following sub-sections of PayShap:
- Outbound pay-by-proxy PayShap.
- Outbound pay-by-account PayShap.
- Inbound pay-by-proxy PayShap, using either proxy resolution or the Electrum Account Mirror to verify the identity of the recipient.
- Inbound pay-by-account PayShap.
- Inbound PayShap following an outbound Request-to-Pay.
Pay-by-account requires that the sender provides the beneficiary's account number and the receiving bank's identifier when initiating the payment.
Pay-by-proxy allows for the use of a proxy to identify the beneficiary's account. A proxy must include a unique and easily-remembered personal identifier. For PayShap, this is usually the beneficiary’s mobile phone number (MSISDN).
Request-to-pay (RTP) allows a beneficiary to request payment from a payer at an industry bank.
For more information about this service, see our implementation guides for inbound and outbound PayShap, and our API reference documentation.