Question 1

How do we communicate with Qippay's API?

Accepted Answer

Our API is an industry standard REST API, which returns JSON responses. We've streamlined the requests and responses to focus on just what you need to get the job done.

Question 2

How is authentication handled with Qippay's API?

Accepted Answer

When your account with Qippay is onboarded, you will be provided with a client_secret to use with our API, and a beneficiary_id for each bank account number you need to receive payments into. Your calls to the API will all require the client_secret in the authentication header of the request.

Question 3

How do your payment rails work – do we need to communicate with the user's bank?

Accepted Answer

Our API acts as a single connection point so your users can make payments from any of the banks we support.
You make the calls to Qippay's API, then we handle the communication with the bank they have selected and respond with the data you need to make the payment – you don't need any communication with the bank.

Question 4

What could a rogue party do if they get our client_secret and beneficiary_id?

Accepted Answer

While you should always ensure that your client_secret and beneficiary_id are kept secure, our design and policies ensure that anyone in possession of these can only request users to make payments using your Merchant Name to your bank account. While it would be less than ideal, a rogue party cannot make payments to a different account using your credentials.

Question 5

Can Qippay's API be integrated into mobile apps as well as web platforms?

Accepted Answer

Yes it can!  As a standard REST API, your app can make whatever calls are required, and the user’s mobile OS will handle any redirects to the Bank’s app, and back to your own app on completion.

Payments

Integration

Enterprise Solution

Support

Clients

Industry

DEVELOPERS

How do we communicate with Qippay's API?

How is authentication handled with Qippay's API?

How do your payment rails work – do we need to communicate with the user's bank?

What could a rogue party do if they get our client_secret and beneficiary_id?

Can Qippay's API be integrated into mobile apps as well as web platforms?

How do we communicate with Qippay's API?

How is authentication handled with Qippay's API?

How do your payment rails work – do we need to communicate with the user's bank?

What could a rogue party do if they get our client_secret and beneficiary_id?

Can Qippay's API be integrated into mobile apps as well as web platforms?

What tools are there to help get started with Qippay's API?

What dependencies will we need to use Qippay's API?

Do you have a test environment?

Do we need to do different things depending on the bank?

How much more coding is involved in Qip PayBy Embedded vs Qip PayBy Hosted?

Sign up with Qippay

How do we add or change our account number or trading name that we receive payments to?

What if our Trading Name doesn't match our bank account name? What about Confirmation of Payee services?