OK
- Retrieve a recurring payment request by its ID
Adfin API (1.0.0)
Adfin uses OAuth 2.0 access tokens to authenticate all API requests.
There are two contexts in which tokens are issued:
Biller Access Tokens — Generated via the Authorization Code flow when a biller connects their Adfin account. These tokens grant access to that biller's data (invoices, payment requests, customers, etc.).
Platform Access Tokens — Generated via the Client Credentials flow for Adfin's own integrations and system events. These tokens authenticate Adfin as the platform itself (not as a specific biller) and are required for endpoints like
/api/webhook.
- Mock serverhttps://developer.adfin.com/_mock/api-docs/prod/schedules/payment_requests/{id}
- Production API Server URLhttps://api.adfin.com/api/schedules/payment_requests/{id}
- Staging API Server URLhttps://api.staging.adfin.com/api/schedules/payment_requests/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://developer.adfin.com/_mock/api-docs/prod/schedules/payment_requests/{id}' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'A system-generated, unique identifier for the recurring payment request. Automatically created using the prefix SCH followed by a numeric sequence (e.g., SCH-1, SCH-2, ...).
The next date a new payment request will be generated.
Indicates the current status of the recurring payment request. Possible values might include:
ACTIVE– currently generating new payment requestFINISHED– has finished all planned occurrencesCANCELLED– has been cancelled before finishing all planned occurrences
The date and time when the recurring payment request was created.
The date and time when the recurring payment request was last updated.
The total number of payment requests this recurring payment request is expected to generate based on cadence, start date, and end date.
{ "id": 1, "recurringPaymentRequestNo": "SCH-42", "nextDate": "2025-10-15T00:00:00Z", "status": "ACTIVE", "cadence": { "timeUnit": "WEEK", "frequency": 2, "startDate": "2025-01-01T00:00:00Z", "endDate": "2025-12-31T23:59:59Z" }, "paymentRequestDetails": { "customer": { … }, "paymentTerm": { … }, "distribution": { … }, "amount": 1200, "taxRate": 20, "currencyCode": "GBP", "description": "Quarterly service fee", "reference": "Q1-2025" }, "creationTime": "2025-09-27T12:00:00Z", "lastUpdatedTime": "2025-10-01T08:30:00Z", "totalPaymentRequests": 10, "nextPaymentRequests": [ { … } ] }
- Mock serverhttps://developer.adfin.com/_mock/api-docs/prod/schedules/payment_requests/{id}
- Production API Server URLhttps://api.adfin.com/api/schedules/payment_requests/{id}
- Staging API Server URLhttps://api.staging.adfin.com/api/schedules/payment_requests/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X PUT \
'https://developer.adfin.com/_mock/api-docs/prod/schedules/payment_requests/{id}' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"cadence": {
"timeUnit": "WEEK",
"frequency": 2,
"startDate": "2025-01-01T00:00:00Z",
"endDate": "2025-12-31T23:59:59Z"
},
"paymentRequestDetails": {
"customer": {
"id": "80349480-490b-4234-92e7-fad697e3d446"
},
"paymentTerm": {
"timeUnit": "DAY",
"value": 30
},
"distribution": {
"collectionMethod": "AUTO_COLLECT",
"templateId": "dc9c7c6e-4c12-4cc9-8d22-20c5b2a7f8f7",
"customMessage": "Please review and confirm payment.",
"approvedForSending": true
},
"amount": 1200,
"taxRate": 20,
"currencyCode": "GBP",
"description": "Quarterly service fee",
"reference": "Q1-2025"
}
}'The request has succeeded and has resulted in one recurring payment request being updated
A system-generated, unique identifier for the recurring invoice. Automatically created using the prefix SCH followed by a numeric sequence (e.g., SCH-1, SCH-2, ...).
The next date a new invoice will be automatically generated.
Indicates the current status of the recurring invoice. Possible values might include:
DRAFT– currently not generating new invoicesACTIVE– currently generating new invoicesFINISHED– has finished all planned occurrencesCANCELLED– has been cancelled before finishing all planned occurrences
The date and time when the recurring invoice was created.
The date and time when the recurring invoice was last updated.
The total number of invoices this recurring invoice is expected to generate based on cadence, start date, and end date.
The total amount of the recurring invoice. Calculated based on the sum of all invoice line items across all occurrences.
{ "id": 1, "recurringInvoiceNo": "SCH-42", "nextIssueDate": "2025-10-15T00:00:00Z", "status": "ACTIVE", "cadence": { "timeUnit": "WEEK", "frequency": 2, "startDate": "2025-01-01T00:00:00Z", "endDate": "2025-12-31T23:59:59Z" }, "invoiceDetails": { "customer": { … }, "paymentTerm": { … }, "distribution": { … }, "description": "Monthly subscription for January", "currencyCode": "GBP", "itemsTaxType": "INCLUSIVE", "items": [ … ] }, "creationTime": "2025-09-27T12:00:00Z", "lastUpdatedTime": "2025-10-01T08:30:00Z", "totalInvoices": 10, "amount": 1234.5, "nextInvoices": [ { … } ] }
- Mock serverhttps://developer.adfin.com/_mock/api-docs/prod/schedules/payment_requests/{id}
- Production API Server URLhttps://api.adfin.com/api/schedules/payment_requests/{id}
- Staging API Server URLhttps://api.staging.adfin.com/api/schedules/payment_requests/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X DELETE \
'https://developer.adfin.com/_mock/api-docs/prod/schedules/payment_requests/{id}' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'- Mock serverhttps://developer.adfin.com/_mock/api-docs/prod/schedules/payment_requests/{id}:cancel
- Production API Server URLhttps://api.adfin.com/api/schedules/payment_requests/{id}:cancel
- Staging API Server URLhttps://api.staging.adfin.com/api/schedules/payment_requests/{id}:cancel
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X PUT \
'https://developer.adfin.com/_mock/api-docs/prod/schedules/payment_requests/{id}:cancel' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'Determines whether the cadence repeats in weeks, months or years. Common values:
- WEEK
- MONTH
- YEAR
Combined with timeUnit to determine how often the cadence occurs. For example:
frequency = 2andtimeUnit = WEEK→ every 2 weeksfrequency = 1andtimeUnit = MONTH→ every month
The first occurrence happens at this time.
How the payment is expected to be collected. For example:
AUTO_COLLECT: Collected automatically via direct debit.ON_DEMAND: Collected via other payment methods (eg.CARD,APPLE_PAY,GOOGLE_PAY,BANK).NONE: No payment collection is initiated automatically.
The workflow template ID used for sending the invoice or payment request to the customer. Optional — if null, the system default template will be used.
An optional message that will be sent to the customer when the invoice or payment request is distributed. Can be used for personalized greetings or additional instructions.
The total amount to be collected for each of the payment requests generated.
The INCLUSIVE tax rate (%) applied to the payment request.
The three-letter ISO 4217 currency code (e.g., GBP, EUR, USD). Indicates the currency in which the payment request is issued.
A short, description of the payment request.
- Mock serverhttps://developer.adfin.com/_mock/api-docs/prod/schedules/payment_requests
- Production API Server URLhttps://api.adfin.com/api/schedules/payment_requests
- Staging API Server URLhttps://api.staging.adfin.com/api/schedules/payment_requests
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
https://developer.adfin.com/_mock/api-docs/prod/schedules/payment_requests \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"cadence": {
"type": "INTERVAL",
"timeUnit": "MONTHS",
"frequency": 1,
"startDate": "2025-01-01T00:00:00Z"
},
"paymentRequestDetails": {
"customer": {
"id": "80349480-490b-4234-92e7-fad697e3d446"
},
"paymentTerm": {
"timeUnit": "DAYS",
"value": 30
},
"distribution": {
"collectionMethod": "AUTO_COLLECT",
"templateId": "d290f1ee-6c54-4b01-90e6-d701748f0851",
"customMessage": "Thank you for your business!",
"approvedForSending": true
},
"amount": "10.00",
"taxRate": "0.1",
"currencyCode": "GBP",
"description": "Monthly subscription for January",
"reference": "PR-01"
}
}'The request was successful and the recurring payment request was created
A system-generated, unique identifier for the recurring payment request. Automatically created using the prefix SCH followed by a numeric sequence (e.g., SCH-1, SCH-2, ...).
The next date a new payment request will be generated.
Indicates the current status of the recurring payment request. Possible values might include:
ACTIVE– currently generating new payment requestFINISHED– has finished all planned occurrencesCANCELLED– has been cancelled before finishing all planned occurrences
The date and time when the recurring payment request was created.
The date and time when the recurring payment request was last updated.
The total number of payment requests this recurring payment request is expected to generate based on cadence, start date, and end date.
{ "id": 1, "recurringPaymentRequestNo": "SCH-42", "nextDate": "2025-10-15T00:00:00Z", "status": "ACTIVE", "cadence": { "timeUnit": "WEEK", "frequency": 2, "startDate": "2025-01-01T00:00:00Z", "endDate": "2025-12-31T23:59:59Z" }, "paymentRequestDetails": { "customer": { … }, "paymentTerm": { … }, "distribution": { … }, "amount": 1200, "taxRate": 20, "currencyCode": "GBP", "description": "Quarterly service fee", "reference": "Q1-2025" }, "creationTime": "2025-09-27T12:00:00Z", "lastUpdatedTime": "2025-10-01T08:30:00Z", "totalPaymentRequests": 10, "nextPaymentRequests": [ { … } ] }