Creates/Initiates a Swish payment request that will start a payment
and initiate the payment request on the end users Swish app on their
cell phone. Get the status of the payment by polling the GET endpoint.
For more information see
Cancel a standalone outgoing payment. This is a pure API feature.
Status of the outgoing payment is made through a call to ‘Get outgoing
payment statuses’
Remove an unhandled payment from the system and book it if needed.
This can be used if the unhandled payments are for an invoice that was
not created or exists in Billecta
Gets all incoming payments that has been matched/connected to an
invoice. Unhandled/Unknown payments that are not related to any
invoice will not be retrieved in this method. Please refer to ‘Get
unhandled payments’ endpoint.
Retrieves the status of single outgoing payment.
Retrieves the status of all outgoing payments between two dates.
Gets the status for the Swish payment request. A payment request must
first be created/initiated by the POST endpoint. Use the returned
token in the POST endpoint to retrieve status.
Retrieve a specific unhandled payment by payment id. An unhandled
payment is an incoming payment that can’t be connected to any invoice
due to that the reference (OCR/invoice number/sender/etc) is unknown
and can’t be found in the system. An unhandled payment can also be an
overpayment connected to an invoice. Unhandled payments are handled
through the MatchPayments endpoint.
Retrieves all unhandled payments. An unhandled payment is an incoming
payment that can’t be connected to any invoice due to that the
reference (OCR/invoice number/sender/etc) is unknown and can’t be
found in the system. Unhandled payments are handled through the
MatchPayments endpoint.
Connects an unhandled payment that the system automatically couldn’t
connect.
Creates an unhandled or over payment. This endpoint is only available
in test enviroment
Sets the status of single outgoing payment. This endpoint is only
available in test enviroment