# Payment Intent

The `/PaymentIntent` endpoint supports handling both one-time and recurring payments. For recurring payments, a Recurring block replaces, or is
added alongside, the OneTime block in the request. Some Payment Service Providers (PSPs) require or optionally support an initial payment
(a OneTime block) AND recurring payment in the same request for authorization. You can find out the initial payment details for a given PSP
using `GET /PaymentMethods`. Please see the specific [payment processor articles](/docs/@production/payment-processors/index.md) for further details.

When using the endpoint to initiate new payments, check the org configuration and make sure you have the correct details by querying the
[Payment Method](/api/payment-api-v2/payment-methods) and [Source Connectors](/api/payment-api-v2/source-connectors) endpoints. Some payment methods enable or require further
[Package Actions](/api/payment-api-v2/package-actions). Be sure to also include these in the payment intent request.

In addition to setting up new one-time or recurring payments, you can pay existing one-time payments (installments) and update existing recurring payments.
To pay an existing installment, simply exclude the Payer block and add the Id of the installment to the OneTime block. We recommend first checking the
details of the installment using `GET /Installment` with the GUID or record Id.

To update the payment method, processor or other details of a recurring payment, remove the Payer block and add the identifier of the recurring payment
to the Recurring block along with a PaymentMethod block that includes the details to be changed. As with installments, we recommend first checking current
details by using `GET /Recurring` with the GUID or record Id.

The endpoint also supports checking the status of payment intent inbound report processing. Use `GET /PaymentIntent/{ID}` where ID is payment intent Id
of the one-time or recurring payment.


## Create, pay or update payments

 - [POST /PaymentIntent](https://docs.findock.com/api/payment-api-v2/payment-intent/paymentintent.md): The /PaymentIntent endpoint supports four POST operations: (1) create a new one-time payment, (2) create a new recurring payment, (3) pay an existing installment, and (4) update
an existing recurring payment. All actions automatically update Salesforce data accordingly.

## Check inbound report status

 - [GET /PaymentIntent/{ID}](https://docs.findock.com/api/payment-api-v2/payment-intent/paymentstatus.md): Use this operation to get the status of the inbound report of a payment intent along with information about the related installment or recurring payment
(Recurring Payment, Gift Commitment or Recurring Donation object record). To get details of the related records themselves, use the /Installment
and /Recurring endpoints.