POST payments Begunstiger

POST
/payments/begunstiger

Authorization

Bearer
headerAuthorizationBearer <token>

Paste your JWT token here

Request Body

The data transfer object containing begunstiger payment details.

application/json
  1. body

Defines the DTO for posting a "Begunstiger" (benefactor) fee payment, containing the necessary information for creating a new begunstiger payment, including the member ID and an optional flag indicating whether the payment was manually marked as paid. This is a distinct payment type from PostMembershipPaymentDTO so that a begunstiger cannot pay the (cheaper) regular membership fee through the membership payment endpoint instead of their own fee.

memberId?string

The identifier of the member who made the payment. This is a foreign key referencing the Member entity. This property is nullable because even if the member is removed from the database, we may want to keep the payment record for historical and auditing purposes. In such cases, the MemberId would be set to null to indicate that the member associated with the payment has been deleted, while still retaining the payment information for reference.

Formatuuid
manuallyMarkedAsPaid?boolean

Indicates whether the payment was manually marked as paid by an administrator. This is used to differentiate between payments that were processed through the normal payment flow and those that were manually marked as paid, which may require different handling in terms of accounting and reporting. This property is set to false by default, and can be set to true by an administrator when they manually mark a payment as paid, allowing for better tracking and management of payments that may not have gone through the standard payment processing flow.

Response Body

OK

application/json
  1. response

Defines the response DTO for a payment, containing the necessary information about the payment response, including an optional checkout URL. The PostPaymentResponse is used to transfer data from the server to the client after creating a new payment, allowing for the inclusion of relevant information such as a checkout URL if applicable, providing a structured and informative response for payment-related operations in the application.

checkoutUrl?|

The URL provided by the Payment Service for the payment intent. This URL is used to redirect the member to the Payment Service payment page where they can complete the payment process. This property is required for all payments, as it is essential for facilitating the payment process through the Payment Service payment gateway and ensuring that members can easily access the payment page to complete their transactions.

curl -X POST 'https://example.com/payments/begunstiger' \  -H 'Content-Type: application/json' \  -d '{}'
{  "checkoutUrl": "string"}