taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 15769cd4f52b9189a2bccdd13edeef32098e4089
parent 7ea3f990da7035e4696c35b9ba0503644b0eff6d
Author: Christian Grothoff <christian@grothoff.org>
Date:   Sun,  3 May 2026 13:23:22 +0200

more fixes

Diffstat:
Mcore/merchant/post-management-instances.rst | 2++
Mpos-integration.rst | 7++++---
Mtaler-merchant-manual.rst | 2+-
3 files changed, 7 insertions(+), 4 deletions(-)

diff --git a/core/merchant/post-management-instances.rst b/core/merchant/post-management-instances.rst @@ -1,3 +1,5 @@ +.. _post-management-instances: + .. http:post:: /management/instances This request will be used to create a new merchant instance in the backend. diff --git a/pos-integration.rst b/pos-integration.rst @@ -42,7 +42,7 @@ Merchant API Basics ------------------- A Taler merchant backend offers a HTTP API. Requests to private endpoints are -`authenticated <merchant-api-authentication>` with a bearer token in the +`authenticated <merchant-api-authentication>`_ with a bearer token in the ``Authorization: Bearer $TOKEN`` header. Some endpoints offered by the Taler merchant backend are publicly accessible, @@ -74,7 +74,7 @@ onboarding flow with the PoS provider. While more convenient, it comes with more integration effort. This flow requires that the provider of the PoS terminal is operating (or -subcontracting the operation of) a separate `Taler merchant backend <merchant-backend-operator-manual>`. +subcontracting the operation of) a separate `Taler merchant backend <merchant-backend-operator-manual>`_. The Taler exchange, the regulated payment service provider, will still be operated separately (i.e. by Taler Operations AG in Switzerland). To simplify the @@ -85,7 +85,8 @@ For the integrated onboarding, the steps for the merchant are: * Merchant onboards with PoS terminal and enables Taler support. * The PoS terminal provider creates a new tenant (=instance) in the Taler - merchant backend via the :http:post:`management/instances` endpoint and + merchant backend via the + `POST /management/instances <post-management-instances>`_ endpoint and configures it (i.e. setting up contact info for notifications, bank account info, etc. via the respective endpoints). This is done using administrative credentials on the merchant backend. diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst @@ -983,7 +983,7 @@ Instances can be created by POSTing a request to ``/management/instances`` without using the Web interface. This could be useful if you want to create many instances programmatically. To create an instance without the Web interface create a file ``instance.json`` with an -`InstanceConfigurationMessage`: +`InstanceConfigurationRequest`: .. code-block:: json