Change Details

**Acceptance criteria:** - The payment bounded context has a new use case that allows to capture a one-time payment. **Implementation Details** - Change `PayPalPaymentProviderAdapterConfig` (the class that contains the data from the PayPal API YAML configuration), changing `returnUrl` to `returnUrlRecurring` (you can refactor `returnUrl` to `returnUrlRecurring`) and `returnUrlOneTime`. Adapt the tests and `PayPalPaymentProviderAdapterConfigSchema` (the class that validates the array structure form the YAML). - Change the parameters in `PayPalPaymentProviderAdapter` to use `returnUrlOneTime` in the `createOrderWithAPI` method - add a `findOrderByOrderId` to the `PayPalPaymentIdentifierRepository` and implementations. You may move the implementation out of `DoctrinePaymentRepository` and into its own class - Add a `captureOrder` API method to the `PaypalAPI` and implementation. It should receive an order id (string) and call the "capture order" Paypal endpoint (see https://developer.paypal.com/docs/api/orders/v2/#orders_capture ) . It should return the `id` string from the `purchase_units.payments.capture` section of the response. This is the Transaction ID. - Create use case (e.g. `CapturePayPalPaymentUseCase` or `CapturePayPalOrderUseCase`) in the payment bounded context. It should: - Receive an OrderID (string) as parameter - call the `CaptureOrder` method of the API. This will return the transaction ID - load the Order with the OrderId - add the transaction id to the order - store the order - If everything went well, return a success result object with the payment id and transaction id - If the API call failed, or something was not found in the database, return an error result object

**Acceptance criteria:** - The payment bounded context has a new use case that allows to capture a one-time payment. **Implementation Details** This needs a number of changes, building on each other: - Change configuration {T361100} - add a `findOrderByOrderId` to the `PayPalPaymentIdentifierRepository` and implementations. You may move the implementation out of `DoctrinePaymentRepository` and into its own class - Add a `captureOrder` API method to the `PaypalAPI` and implementation. It should receive an order id (string) and call the "capture order" Paypal endpoint (see https://developer.paypal.com/docs/api/orders/v2/#orders_capture ) . It should return the `id` string from the `purchase_units.payments.capture` section of the response. This is the Transaction ID. - Create use case (e.g. `CapturePayPalPaymentUseCase` or `CapturePayPalOrderUseCase`) in the payment bounded context. It should: - Receive an OrderID (string) as parameter - call the `CaptureOrder` method of the API. This will return the transaction ID - load the Order with the OrderId - add the transaction id to the order - store the order - If everything went well, return a success result object with the payment id and transaction id - If the API call failed, or something was not found in the database, return an error result object

**Acceptance criteria:** - The payment bounded context has a new use case that allows to capture a one-time payment. **Implementation Details** - Change `PayPalPaymentProviderAdapterConfig` (the class that contains the data from the PayPal API YAML configuration), changing `returnUrl` to `returnUrlRecurring` (you can refactor `returnUrl` to `returnUrlRecurring`) and `returnUrlOneTime`.This needs a number of changes, Adapt the tests and `PayPalPaymentProviderAdapterConfigSchema` (the class that validates the array structure form the YAML).building on each other: - Change the parameters in `PayPalPaymentProviderAdapter` to use `returnUrlOneTime` in the `createOrderWithAPI` methodconfiguration {T361100} - add a `findOrderByOrderId` to the `PayPalPaymentIdentifierRepository` and implementations. You may move the implementation out of `DoctrinePaymentRepository` and into its own class - Add a `captureOrder` API method to the `PaypalAPI` and implementation. It should receive an order id (string) and call the "capture order" Paypal endpoint (see https://developer.paypal.com/docs/api/orders/v2/#orders_capture ) . It should return the `id` string from the `purchase_units.payments.capture` section of the response. This is the Transaction ID. - Create use case (e.g. `CapturePayPalPaymentUseCase` or `CapturePayPalOrderUseCase`) in the payment bounded context. It should: - Receive an OrderID (string) as parameter - call the `CaptureOrder` method of the API. This will return the transaction ID - load the Order with the OrderId - add the transaction id to the order - store the order - If everything went well, return a success result object with the payment id and transaction id - If the API call failed, or something was not found in the database, return an error result object