Skip to content
Last updated

Working with payment terminals

Spense supports a range of payment terminals from different providers.

See the API Reference for payment methods in order to take use of including support for terminals in your integration!

There are different workflows for different cases, below are two flow charts for a couple of them.

Yes
No
Yes
No
GET /payment-methods
Are there terminals listed and active?
List terminals to user
Show error and stop
User selects terminal
PUT /payment-methods/payflow_id

Include ID of the selected terminal. This
will send payment data to the chosen terminal.
Did user complete payment?
Payment update webhook
Terminal failure webhook

API Reference

GET /payment-methods

To get a list of available payment payments, which may include other methods than just terminals.

Trigger a terminal payment during creation

This example is slightly different as we include an extra API call - the one that creates the payment, and at the same time we send the selected payment method to the payment.

Yes
No
Yes
No
Yes
No
GET /payment-methods
Are there terminals listed and active?
List terminals to user
Show error and stop
User selects terminal
POST /api/payments

Include ID of the selected terminal in paymentMethodId. This
will send payment data to the chosen terminal.
Did user complete payment?
Payment update webhook
Terminal failure webhook
User selects terminal
PUT /payment-methods/payflow_id

Include ID of the selected terminal. This
will send payment data to the chosen terminal.
Did user complete payment?

API Reference

GET /payment-methods

To get a list of available payment payments, which may include other methods than just terminals.

POST /api/payments

Create the payment, and pass on the selected paymentMethodId when doing it.

Previous page
Next page
Copyright © Spense AS