Billing Request Template
Billing Request Templates are reusable templates that result in numerous Billing Requests with similar attributes. They provide a no-code solution for generating various types of multi-user payment links.
Each template includes a reusable URL that can be embedded in a website or shared with customers via email. Every time the URL is opened, it generates a new Billing Request.
Billing Request Templates overcome the key limitation of the Billing Request: a Billing Request cannot be shared among multiple users because it is intended for single-use and is designed to cater to the unique needs of individual customers.
List Billing Request Templates#
/billing_request_templatesReturns a cursor-paginated list of your Billing Request Templates.
Response 200
Successful response
billing_request_templatesarray18 properties
idstring
Unique identifier, beginning with "BRT".
namestring
Name for the template. Provides a friendly human name for the template, as it is shown in the dashboard. Must not exceed 255 characters.
mandate_request_currencyobject
ISO 4217 currency code.
mandate_request_schemestring
A bank payment scheme. Currently "ach", "autogiro", "bacs", "becs", "becs_nz", "betalingsservice", "faster_payments", "pad", "pay_to" and "sepa_core" are supported. Optional for mandate only requests - if left blank, the payer will be able to select the currency/scheme to pay with from a list of your available schemes.
mandate_request_verifyobject
Verification preference for the mandate.
mandate_request_metadataobject
Key-value store of custom data that will be applied to the mandate created when this request is fulfilled. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.
payment_request_descriptionstring
A human-readable description of the payment and/or mandate. This will be displayed to the payer when authorising the billing request.
mandate_request_descriptionstring
A human-readable description of the payment and/or mandate. This will be displayed to the payer when authorising the billing request.
mandate_request_constraintsobject
Constraints that will apply to the mandate_request. (Optional) Specifically required for PayTo and VRP.
5 properties
start_datestring
The date from which payments can be taken.
This is an optional field and if it is not supplied the start date will be set to the day authorisation happens.
end_datestring
The latest date at which payments can be taken, must occur after start_date if present
This is an optional field and if it is not supplied the agreement will be considered open and will not have an end date. Keep in mind the end date must take into account how long it will take the user to set up this agreement via the Billing Request.
max_amount_per_paymentinteger
The maximum amount that can be charged for a single payment in the lowest denomination for the currency (e.g. pence in GBP, cents in EUR). Note: Required for PayTo and VRP.
payment_methodstring
A constraint where you can specify info (free text string) about how payments are calculated. For use when payments vary and cannot be expressed as a fixed amount and frequency. Note: This is only supported for ACH and PAD schemes.
periodic_limitsarray
Caps on the total amount and/or number of payments that can be collected within a
repeating period (e.g. no more than a set amount per month), as opposed to
max_amount_per_payment which caps a single payment.
Note: Required for VRP, where exactly one periodic limit must be provided. Optional for PayTo.
4 properties
periodstring
The repeating period for this mandate. Required whenever a periodic limit is provided (for both VRP and PayTo). If periodic_limits is omitted entirely for PayTo, this defaults to flexible.
dayweekmonthyearflexiblemax_total_amountinteger
The maximum total amount that can be charged for all payments in this periodic limit, in the lowest denomination for the currency (e.g. pence in GBP, cents in EUR).
Note: Required for VRP. This is not permitted for the PayTo scheme.
max_paymentsinteger
The maximum number of payments that can be collected in this periodic limit.
Note: Only supported for the PayTo scheme, where it is optional.
alignmentstring
The alignment of the period. Defaults to creation_date if not specified.
calendar - the period follows fixed calendar boundaries, the same for every mandate:
week runs Monday to Sunday, month runs from the 1st to the last day of the calendar
month, and year runs from 1 January to 31 December. If the mandate starts partway
through a period, the limit for that first period is reduced proportionally to the days
remaining (e.g. a monthly limit starting on the 15th gives roughly half the limit for
that first month).
creation_date - the period follows the mandate's own start date rather than the
calendar. For example, if the mandate starts on the 15th, each monthly period runs from
the 15th to the 14th of the following month. The first period is a full period, not
reduced proportionally.
Note: Has no effect when period is flexible.
calendarcreation_datepayment_request_amountstring
Amount in full.
payment_request_currencyobject
ISO 4217 currency code. GBP and EUR supported; GBP with your customers in the UK and for EUR with your customers in supported Eurozone countries only.
payment_request_schemestring
(Optional) A scheme used for Open Banking payments. Currently faster_payments is supported in the UK (GBP) and sepa_credit_transfer and sepa_instant_credit_transfer are supported in supported Eurozone countries (EUR). For Eurozone countries, sepa_credit_transfer is used as the default. Please be aware that sepa_instant_credit_transfer may incur an additional fee for your customer.
payment_request_metadataobject
Key-value store of custom data that will be applied to the payment created when this request is fulfilled. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.
redirect_uristring
URL that the payer can be redirected to after completing the request flow.
authorisation_urlstring
Permanent URL that customers can visit to allow them to complete a flow based on this template, before being returned to the redirect_uri.
metadataobject
Key-value store of custom data. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.
created_atstring
Fixed timestamp, recording when this resource was created.
updated_atstring
Dynamic timestamp recording when this resource was last updated.
metaobject2 properties
limitintegercursorsobject
2 properties
beforestring
Cursor pointing to the end of the desired set.
afterstring
Cursor pointing to the start of the desired set.
Errors 400401404422500
Bad Request
Unauthorised
Not found
Validation Error
Internal Error
Error Body
codeintegerdocumentation_urlstringerrorsarray2 properties
reasonstringmessagestringmessagestringrequest_idstringtypestringmetadataobjectlinksobjectCreate a Billing Request Template#
/billing_request_templatesRequest Body
billing_request_templatesobject15 properties
namestring
Name for the template. Provides a friendly human name for the template, as it is shown in the dashboard. Must not exceed 255 characters.
mandate_request_currencyobject
ISO 4217 currency code.
mandate_request_schemestring
A bank payment scheme. Currently "ach", "autogiro", "bacs", "becs", "becs_nz", "betalingsservice", "faster_payments", "pad", "pay_to" and "sepa_core" are supported. Optional for mandate only requests - if left blank, the payer will be able to select the currency/scheme to pay with from a list of your available schemes.
mandate_request_verifystring
Verification preference for the mandate.
mandate_request_metadataobject
Key-value store of custom data that will be applied to the mandate created when this request is fulfilled. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.
payment_request_descriptionstring
A human-readable description of the payment and/or mandate. This will be displayed to the payer when authorising the billing request.
mandate_request_descriptionstring
A human-readable description of the payment and/or mandate. This will be displayed to the payer when authorising the billing request.
mandate_request_constraintsobject
Constraints that will apply to the mandate_request. (Optional) Specifically required for PayTo and VRP.
5 properties
start_datestring
The date from which payments can be taken.
This is an optional field and if it is not supplied the start date will be set to the day authorisation happens.
end_datestring
The latest date at which payments can be taken, must occur after start_date if present
This is an optional field and if it is not supplied the agreement will be considered open and will not have an end date. Keep in mind the end date must take into account how long it will take the user to set up this agreement via the Billing Request.
max_amount_per_paymentinteger
The maximum amount that can be charged for a single payment in the lowest denomination for the currency (e.g. pence in GBP, cents in EUR). Note: Required for PayTo and VRP.
payment_methodstring
A constraint where you can specify info (free text string) about how payments are calculated. For use when payments vary and cannot be expressed as a fixed amount and frequency. Note: This is only supported for ACH and PAD schemes.
periodic_limitsarray
Caps on the total amount and/or number of payments that can be collected within a
repeating period (e.g. no more than a set amount per month), as opposed to
max_amount_per_payment which caps a single payment.
Note: Required for VRP, where exactly one periodic limit must be provided. Optional for PayTo.
4 properties
periodstring
The repeating period for this mandate. Required whenever a periodic limit is provided (for both VRP and PayTo). If periodic_limits is omitted entirely for PayTo, this defaults to flexible.
dayweekmonthyearflexiblemax_total_amountinteger
The maximum total amount that can be charged for all payments in this periodic limit, in the lowest denomination for the currency (e.g. pence in GBP, cents in EUR).
Note: Required for VRP. This is not permitted for the PayTo scheme.
max_paymentsinteger
The maximum number of payments that can be collected in this periodic limit.
Note: Only supported for the PayTo scheme, where it is optional.
alignmentstring
The alignment of the period. Defaults to creation_date if not specified.
calendar - the period follows fixed calendar boundaries, the same for every mandate:
week runs Monday to Sunday, month runs from the 1st to the last day of the calendar
month, and year runs from 1 January to 31 December. If the mandate starts partway
through a period, the limit for that first period is reduced proportionally to the days
remaining (e.g. a monthly limit starting on the 15th gives roughly half the limit for
that first month).
creation_date - the period follows the mandate's own start date rather than the
calendar. For example, if the mandate starts on the 15th, each monthly period runs from
the 15th to the 14th of the following month. The first period is a full period, not
reduced proportionally.
Note: Has no effect when period is flexible.
calendarcreation_datepayment_request_amountstring
Amount in full.
payment_request_currencyobject
ISO 4217 currency code. GBP and EUR supported; GBP with your customers in the UK and for EUR with your customers in supported Eurozone countries only.
payment_request_schemestring
(Optional) A scheme used for Open Banking payments. Currently faster_payments is supported in the UK (GBP) and sepa_credit_transfer and sepa_instant_credit_transfer are supported in supported Eurozone countries (EUR). For Eurozone countries, sepa_credit_transfer is used as the default. Please be aware that sepa_instant_credit_transfer may incur an additional fee for your customer.
payment_request_metadataobject
Key-value store of custom data that will be applied to the payment created when this request is fulfilled. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.
redirect_uristring
URL that the payer can be redirected to after completing the request flow.
metadataobject
Key-value store of custom data. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.
linksobject
1 properties
creditorstring
ID of the associated creditor. Only required if your account manages multiple creditors.
Response 201
Resource created successfully
billing_request_templatesobject18 properties
idstring
Unique identifier, beginning with "BRT".
namestring
Name for the template. Provides a friendly human name for the template, as it is shown in the dashboard. Must not exceed 255 characters.
mandate_request_currencyobject
ISO 4217 currency code.
mandate_request_schemestring
A bank payment scheme. Currently "ach", "autogiro", "bacs", "becs", "becs_nz", "betalingsservice", "faster_payments", "pad", "pay_to" and "sepa_core" are supported. Optional for mandate only requests - if left blank, the payer will be able to select the currency/scheme to pay with from a list of your available schemes.
mandate_request_verifyobject
Verification preference for the mandate.
mandate_request_metadataobject
Key-value store of custom data that will be applied to the mandate created when this request is fulfilled. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.
payment_request_descriptionstring
A human-readable description of the payment and/or mandate. This will be displayed to the payer when authorising the billing request.
mandate_request_descriptionstring
A human-readable description of the payment and/or mandate. This will be displayed to the payer when authorising the billing request.
mandate_request_constraintsobject
Constraints that will apply to the mandate_request. (Optional) Specifically required for PayTo and VRP.
5 properties
start_datestring
The date from which payments can be taken.
This is an optional field and if it is not supplied the start date will be set to the day authorisation happens.
end_datestring
The latest date at which payments can be taken, must occur after start_date if present
This is an optional field and if it is not supplied the agreement will be considered open and will not have an end date. Keep in mind the end date must take into account how long it will take the user to set up this agreement via the Billing Request.
max_amount_per_paymentinteger
The maximum amount that can be charged for a single payment in the lowest denomination for the currency (e.g. pence in GBP, cents in EUR). Note: Required for PayTo and VRP.
payment_methodstring
A constraint where you can specify info (free text string) about how payments are calculated. For use when payments vary and cannot be expressed as a fixed amount and frequency. Note: This is only supported for ACH and PAD schemes.
periodic_limitsarray
Caps on the total amount and/or number of payments that can be collected within a
repeating period (e.g. no more than a set amount per month), as opposed to
max_amount_per_payment which caps a single payment.
Note: Required for VRP, where exactly one periodic limit must be provided. Optional for PayTo.
4 properties
periodstring
The repeating period for this mandate. Required whenever a periodic limit is provided (for both VRP and PayTo). If periodic_limits is omitted entirely for PayTo, this defaults to flexible.
dayweekmonthyearflexiblemax_total_amountinteger
The maximum total amount that can be charged for all payments in this periodic limit, in the lowest denomination for the currency (e.g. pence in GBP, cents in EUR).
Note: Required for VRP. This is not permitted for the PayTo scheme.
max_paymentsinteger
The maximum number of payments that can be collected in this periodic limit.
Note: Only supported for the PayTo scheme, where it is optional.
alignmentstring
The alignment of the period. Defaults to creation_date if not specified.
calendar - the period follows fixed calendar boundaries, the same for every mandate:
week runs Monday to Sunday, month runs from the 1st to the last day of the calendar
month, and year runs from 1 January to 31 December. If the mandate starts partway
through a period, the limit for that first period is reduced proportionally to the days
remaining (e.g. a monthly limit starting on the 15th gives roughly half the limit for
that first month).
creation_date - the period follows the mandate's own start date rather than the
calendar. For example, if the mandate starts on the 15th, each monthly period runs from
the 15th to the 14th of the following month. The first period is a full period, not
reduced proportionally.
Note: Has no effect when period is flexible.
calendarcreation_datepayment_request_amountstring
Amount in full.
payment_request_currencyobject
ISO 4217 currency code. GBP and EUR supported; GBP with your customers in the UK and for EUR with your customers in supported Eurozone countries only.
payment_request_schemestring
(Optional) A scheme used for Open Banking payments. Currently faster_payments is supported in the UK (GBP) and sepa_credit_transfer and sepa_instant_credit_transfer are supported in supported Eurozone countries (EUR). For Eurozone countries, sepa_credit_transfer is used as the default. Please be aware that sepa_instant_credit_transfer may incur an additional fee for your customer.
payment_request_metadataobject
Key-value store of custom data that will be applied to the payment created when this request is fulfilled. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.
redirect_uristring
URL that the payer can be redirected to after completing the request flow.
authorisation_urlstring
Permanent URL that customers can visit to allow them to complete a flow based on this template, before being returned to the redirect_uri.
metadataobject
Key-value store of custom data. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.
created_atstring
Fixed timestamp, recording when this resource was created.
updated_atstring
Dynamic timestamp recording when this resource was last updated.
Errors 400401404422500
Bad Request
Unauthorised
Not found
Validation Error
Internal Error
Error Body
codeintegerdocumentation_urlstringerrorsarray2 properties
reasonstringmessagestringmessagestringrequest_idstringtypestringmetadataobjectlinksobjectGet a single Billing Request Template#
/billing_request_templates/{billing_request_template_id}Fetches a Billing Request Template
Path Parameters
| Name | Type | Description |
|---|---|---|
billing_request_template_idrequired | string | The billing request template id |
Response 200
Successful response
billing_request_templatesobject18 properties
idstring
Unique identifier, beginning with "BRT".
namestring
Name for the template. Provides a friendly human name for the template, as it is shown in the dashboard. Must not exceed 255 characters.
mandate_request_currencyobject
ISO 4217 currency code.
mandate_request_schemestring
A bank payment scheme. Currently "ach", "autogiro", "bacs", "becs", "becs_nz", "betalingsservice", "faster_payments", "pad", "pay_to" and "sepa_core" are supported. Optional for mandate only requests - if left blank, the payer will be able to select the currency/scheme to pay with from a list of your available schemes.
mandate_request_verifyobject
Verification preference for the mandate.
mandate_request_metadataobject
Key-value store of custom data that will be applied to the mandate created when this request is fulfilled. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.
payment_request_descriptionstring
A human-readable description of the payment and/or mandate. This will be displayed to the payer when authorising the billing request.
mandate_request_descriptionstring
A human-readable description of the payment and/or mandate. This will be displayed to the payer when authorising the billing request.
mandate_request_constraintsobject
Constraints that will apply to the mandate_request. (Optional) Specifically required for PayTo and VRP.
5 properties
start_datestring
The date from which payments can be taken.
This is an optional field and if it is not supplied the start date will be set to the day authorisation happens.
end_datestring
The latest date at which payments can be taken, must occur after start_date if present
This is an optional field and if it is not supplied the agreement will be considered open and will not have an end date. Keep in mind the end date must take into account how long it will take the user to set up this agreement via the Billing Request.
max_amount_per_paymentinteger
The maximum amount that can be charged for a single payment in the lowest denomination for the currency (e.g. pence in GBP, cents in EUR). Note: Required for PayTo and VRP.
payment_methodstring
A constraint where you can specify info (free text string) about how payments are calculated. For use when payments vary and cannot be expressed as a fixed amount and frequency. Note: This is only supported for ACH and PAD schemes.
periodic_limitsarray
Caps on the total amount and/or number of payments that can be collected within a
repeating period (e.g. no more than a set amount per month), as opposed to
max_amount_per_payment which caps a single payment.
Note: Required for VRP, where exactly one periodic limit must be provided. Optional for PayTo.
4 properties
periodstring
The repeating period for this mandate. Required whenever a periodic limit is provided (for both VRP and PayTo). If periodic_limits is omitted entirely for PayTo, this defaults to flexible.
dayweekmonthyearflexiblemax_total_amountinteger
The maximum total amount that can be charged for all payments in this periodic limit, in the lowest denomination for the currency (e.g. pence in GBP, cents in EUR).
Note: Required for VRP. This is not permitted for the PayTo scheme.
max_paymentsinteger
The maximum number of payments that can be collected in this periodic limit.
Note: Only supported for the PayTo scheme, where it is optional.
alignmentstring
The alignment of the period. Defaults to creation_date if not specified.
calendar - the period follows fixed calendar boundaries, the same for every mandate:
week runs Monday to Sunday, month runs from the 1st to the last day of the calendar
month, and year runs from 1 January to 31 December. If the mandate starts partway
through a period, the limit for that first period is reduced proportionally to the days
remaining (e.g. a monthly limit starting on the 15th gives roughly half the limit for
that first month).
creation_date - the period follows the mandate's own start date rather than the
calendar. For example, if the mandate starts on the 15th, each monthly period runs from
the 15th to the 14th of the following month. The first period is a full period, not
reduced proportionally.
Note: Has no effect when period is flexible.
calendarcreation_datepayment_request_amountstring
Amount in full.
payment_request_currencyobject
ISO 4217 currency code. GBP and EUR supported; GBP with your customers in the UK and for EUR with your customers in supported Eurozone countries only.
payment_request_schemestring
(Optional) A scheme used for Open Banking payments. Currently faster_payments is supported in the UK (GBP) and sepa_credit_transfer and sepa_instant_credit_transfer are supported in supported Eurozone countries (EUR). For Eurozone countries, sepa_credit_transfer is used as the default. Please be aware that sepa_instant_credit_transfer may incur an additional fee for your customer.
payment_request_metadataobject
Key-value store of custom data that will be applied to the payment created when this request is fulfilled. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.
redirect_uristring
URL that the payer can be redirected to after completing the request flow.
authorisation_urlstring
Permanent URL that customers can visit to allow them to complete a flow based on this template, before being returned to the redirect_uri.
metadataobject
Key-value store of custom data. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.
created_atstring
Fixed timestamp, recording when this resource was created.
updated_atstring
Dynamic timestamp recording when this resource was last updated.
Errors 400401404422500
Bad Request
Unauthorised
Not found
Validation Error
Internal Error
Error Body
codeintegerdocumentation_urlstringerrorsarray2 properties
reasonstringmessagestringmessagestringrequest_idstringtypestringmetadataobjectlinksobjectUpdate a Billing Request Template#
/billing_request_templates/{billing_request_template_id}Updates a Billing Request Template, which will affect all future Billing Requests created by this template.
Path Parameters
| Name | Type | Description |
|---|---|---|
billing_request_template_idrequired | string | The billing request template id |
Request Body
billing_request_templatesobject14 properties
namestring
Name for the template. Provides a friendly human name for the template, as it is shown in the dashboard. Must not exceed 255 characters.
mandate_request_currencyobject
ISO 4217 currency code.
mandate_request_schemestring
A bank payment scheme. Currently "ach", "autogiro", "bacs", "becs", "becs_nz", "betalingsservice", "faster_payments", "pad", "pay_to" and "sepa_core" are supported. Optional for mandate only requests - if left blank, the payer will be able to select the currency/scheme to pay with from a list of your available schemes.
mandate_request_verifystring
Verification preference for the mandate.
mandate_request_metadataobject
Key-value store of custom data that will be applied to the mandate created when this request is fulfilled. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.
payment_request_descriptionstring
A human-readable description of the payment and/or mandate. This will be displayed to the payer when authorising the billing request.
mandate_request_descriptionstring
A human-readable description of the payment and/or mandate. This will be displayed to the payer when authorising the billing request.
mandate_request_constraintsobject
Constraints that will apply to the mandate_request. (Optional) Specifically required for PayTo and VRP.
5 properties
start_datestring
The date from which payments can be taken.
This is an optional field and if it is not supplied the start date will be set to the day authorisation happens.
end_datestring
The latest date at which payments can be taken, must occur after start_date if present
This is an optional field and if it is not supplied the agreement will be considered open and will not have an end date. Keep in mind the end date must take into account how long it will take the user to set up this agreement via the Billing Request.
max_amount_per_paymentinteger
The maximum amount that can be charged for a single payment in the lowest denomination for the currency (e.g. pence in GBP, cents in EUR). Note: Required for PayTo and VRP.
payment_methodstring
A constraint where you can specify info (free text string) about how payments are calculated. For use when payments vary and cannot be expressed as a fixed amount and frequency. Note: This is only supported for ACH and PAD schemes.
periodic_limitsarray
Caps on the total amount and/or number of payments that can be collected within a
repeating period (e.g. no more than a set amount per month), as opposed to
max_amount_per_payment which caps a single payment.
Note: Required for VRP, where exactly one periodic limit must be provided. Optional for PayTo.
4 properties
periodstring
The repeating period for this mandate. Required whenever a periodic limit is provided (for both VRP and PayTo). If periodic_limits is omitted entirely for PayTo, this defaults to flexible.
dayweekmonthyearflexiblemax_total_amountinteger
The maximum total amount that can be charged for all payments in this periodic limit, in the lowest denomination for the currency (e.g. pence in GBP, cents in EUR).
Note: Required for VRP. This is not permitted for the PayTo scheme.
max_paymentsinteger
The maximum number of payments that can be collected in this periodic limit.
Note: Only supported for the PayTo scheme, where it is optional.
alignmentstring
The alignment of the period. Defaults to creation_date if not specified.
calendar - the period follows fixed calendar boundaries, the same for every mandate:
week runs Monday to Sunday, month runs from the 1st to the last day of the calendar
month, and year runs from 1 January to 31 December. If the mandate starts partway
through a period, the limit for that first period is reduced proportionally to the days
remaining (e.g. a monthly limit starting on the 15th gives roughly half the limit for
that first month).
creation_date - the period follows the mandate's own start date rather than the
calendar. For example, if the mandate starts on the 15th, each monthly period runs from
the 15th to the 14th of the following month. The first period is a full period, not
reduced proportionally.
Note: Has no effect when period is flexible.
calendarcreation_datepayment_request_amountstring
Amount in full.
payment_request_currencyobject
ISO 4217 currency code. GBP and EUR supported; GBP with your customers in the UK and for EUR with your customers in supported Eurozone countries only.
payment_request_schemestring
(Optional) A scheme used for Open Banking payments. Currently faster_payments is supported in the UK (GBP) and sepa_credit_transfer and sepa_instant_credit_transfer are supported in supported Eurozone countries (EUR). For Eurozone countries, sepa_credit_transfer is used as the default. Please be aware that sepa_instant_credit_transfer may incur an additional fee for your customer.
payment_request_metadataobject
Key-value store of custom data that will be applied to the payment created when this request is fulfilled. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.
redirect_uristring
URL that the payer can be redirected to after completing the request flow.
metadataobject
Key-value store of custom data. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.
Response 200
Successful response
billing_request_templatesobject18 properties
idstring
Unique identifier, beginning with "BRT".
namestring
Name for the template. Provides a friendly human name for the template, as it is shown in the dashboard. Must not exceed 255 characters.
mandate_request_currencyobject
ISO 4217 currency code.
mandate_request_schemestring
A bank payment scheme. Currently "ach", "autogiro", "bacs", "becs", "becs_nz", "betalingsservice", "faster_payments", "pad", "pay_to" and "sepa_core" are supported. Optional for mandate only requests - if left blank, the payer will be able to select the currency/scheme to pay with from a list of your available schemes.
mandate_request_verifyobject
Verification preference for the mandate.
mandate_request_metadataobject
Key-value store of custom data that will be applied to the mandate created when this request is fulfilled. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.
payment_request_descriptionstring
A human-readable description of the payment and/or mandate. This will be displayed to the payer when authorising the billing request.
mandate_request_descriptionstring
A human-readable description of the payment and/or mandate. This will be displayed to the payer when authorising the billing request.
mandate_request_constraintsobject
Constraints that will apply to the mandate_request. (Optional) Specifically required for PayTo and VRP.
5 properties
start_datestring
The date from which payments can be taken.
This is an optional field and if it is not supplied the start date will be set to the day authorisation happens.
end_datestring
The latest date at which payments can be taken, must occur after start_date if present
This is an optional field and if it is not supplied the agreement will be considered open and will not have an end date. Keep in mind the end date must take into account how long it will take the user to set up this agreement via the Billing Request.
max_amount_per_paymentinteger
The maximum amount that can be charged for a single payment in the lowest denomination for the currency (e.g. pence in GBP, cents in EUR). Note: Required for PayTo and VRP.
payment_methodstring
A constraint where you can specify info (free text string) about how payments are calculated. For use when payments vary and cannot be expressed as a fixed amount and frequency. Note: This is only supported for ACH and PAD schemes.
periodic_limitsarray
Caps on the total amount and/or number of payments that can be collected within a
repeating period (e.g. no more than a set amount per month), as opposed to
max_amount_per_payment which caps a single payment.
Note: Required for VRP, where exactly one periodic limit must be provided. Optional for PayTo.
4 properties
periodstring
The repeating period for this mandate. Required whenever a periodic limit is provided (for both VRP and PayTo). If periodic_limits is omitted entirely for PayTo, this defaults to flexible.
dayweekmonthyearflexiblemax_total_amountinteger
The maximum total amount that can be charged for all payments in this periodic limit, in the lowest denomination for the currency (e.g. pence in GBP, cents in EUR).
Note: Required for VRP. This is not permitted for the PayTo scheme.
max_paymentsinteger
The maximum number of payments that can be collected in this periodic limit.
Note: Only supported for the PayTo scheme, where it is optional.
alignmentstring
The alignment of the period. Defaults to creation_date if not specified.
calendar - the period follows fixed calendar boundaries, the same for every mandate:
week runs Monday to Sunday, month runs from the 1st to the last day of the calendar
month, and year runs from 1 January to 31 December. If the mandate starts partway
through a period, the limit for that first period is reduced proportionally to the days
remaining (e.g. a monthly limit starting on the 15th gives roughly half the limit for
that first month).
creation_date - the period follows the mandate's own start date rather than the
calendar. For example, if the mandate starts on the 15th, each monthly period runs from
the 15th to the 14th of the following month. The first period is a full period, not
reduced proportionally.
Note: Has no effect when period is flexible.
calendarcreation_datepayment_request_amountstring
Amount in full.
payment_request_currencyobject
ISO 4217 currency code. GBP and EUR supported; GBP with your customers in the UK and for EUR with your customers in supported Eurozone countries only.
payment_request_schemestring
(Optional) A scheme used for Open Banking payments. Currently faster_payments is supported in the UK (GBP) and sepa_credit_transfer and sepa_instant_credit_transfer are supported in supported Eurozone countries (EUR). For Eurozone countries, sepa_credit_transfer is used as the default. Please be aware that sepa_instant_credit_transfer may incur an additional fee for your customer.
payment_request_metadataobject
Key-value store of custom data that will be applied to the payment created when this request is fulfilled. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.
redirect_uristring
URL that the payer can be redirected to after completing the request flow.
authorisation_urlstring
Permanent URL that customers can visit to allow them to complete a flow based on this template, before being returned to the redirect_uri.
metadataobject
Key-value store of custom data. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.
created_atstring
Fixed timestamp, recording when this resource was created.
updated_atstring
Dynamic timestamp recording when this resource was last updated.
Errors 400401404422500
Bad Request
Unauthorised
Not found
Validation Error
Internal Error
Error Body
codeintegerdocumentation_urlstringerrorsarray2 properties
reasonstringmessagestringmessagestringrequest_idstringtypestringmetadataobjectlinksobject