Skip to content

Changes from gocardless/client-library-templates #252

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
gocardless-ci-robot wants to merge 3 commits into
base: master
Choose a base branch
from
+21 −100
Open

Changes from gocardless/client-library-templates #252

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4e79cd2
Changes generated by 954c0afb4d49281568105513c90f0d12ded6fcd2
gocardless-ci-robot[bot] Jun 15, 2026
d18d575
Changes generated by f6b23429e1db4af5f6d559a8933d94ab86835e19
gocardless-ci-robot[bot] Jun 16, 2026
604c3dc
Changes generated by c1a246cf193597d4a75b4787fe464fa9d5cbf101
gocardless-ci-robot[bot] Jun 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 12 additions & 12 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

56 changes: 4 additions & 52 deletions src/services/billingRequestTemplateService.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,33 +64,9 @@ interface BillingRequestTemplateCreateRequest {

mandate_request_scheme?: string;

// Verification preference for the mandate. One of:
// <ul>
// <li>`minimum`: only verify if absolutely required, such as when part of
// scheme rules</li>
// <li>`recommended`: in addition to `minimum`, use the GoCardless payment
// intelligence solution to decide if a payer should be verified</li>
// <li>`when_available`: if verification mechanisms are available, use
// them</li>
// <li>`always`: as `when_available`, but fail to create the Billing Request
// if a mechanism isn't available</li>
// </ul>
//
// By default, all Billing Requests use the `recommended` verification
// preference. It uses GoCardless payment intelligence solution to determine if
// a payer is fraudulent or not. The verification mechanism is based on the
// response and the payer may be asked to verify themselves. If the feature is
// not available, `recommended` behaves like `minimum`.
//
// If you never wish to take advantage of our reduced risk products and Verified
// Mandates as they are released in new schemes, please use the `minimum`
// verification preference.
//
// See [Billing Requests: Creating Verified
// Mandates](https://developer.gocardless.com/getting-started/billing-requests/verified-mandates/)
// for more information.
// Verification preference for the mandate.

mandate_request_verify?: `${Types.BillingRequestTemplateMandateRequestVerify}`;
mandate_request_verify?: string;

// 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.
Expand Down Expand Up @@ -168,33 +144,9 @@ interface BillingRequestTemplateUpdateRequest {

mandate_request_scheme?: string;

// Verification preference for the mandate. One of:
// <ul>
// <li>`minimum`: only verify if absolutely required, such as when part of
// scheme rules</li>
// <li>`recommended`: in addition to `minimum`, use the GoCardless payment
// intelligence solution to decide if a payer should be verified</li>
// <li>`when_available`: if verification mechanisms are available, use
// them</li>
// <li>`always`: as `when_available`, but fail to create the Billing Request
// if a mechanism isn't available</li>
// </ul>
//
// By default, all Billing Requests use the `recommended` verification
// preference. It uses GoCardless payment intelligence solution to determine if
// a payer is fraudulent or not. The verification mechanism is based on the
// response and the payer may be asked to verify themselves. If the feature is
// not available, `recommended` behaves like `minimum`.
//
// If you never wish to take advantage of our reduced risk products and Verified
// Mandates as they are released in new schemes, please use the `minimum`
// verification preference.
//
// See [Billing Requests: Creating Verified
// Mandates](https://developer.gocardless.com/getting-started/billing-requests/verified-mandates/)
// for more information.
// Verification preference for the mandate.

mandate_request_verify?: `${Types.BillingRequestTemplateMandateRequestVerify}`;
mandate_request_verify?: string;

// 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.
Expand Down
41 changes: 5 additions & 36 deletions src/types/Types.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1552,7 +1552,7 @@ export type BillingRequestTemplate = {

// [ISO 4217](https://en.wikipedia.org/wiki/ISO_4217#Active_codes) currency
// code.
mandate_request_currency?: string;
mandate_request_currency?: string | null;

// A human-readable description of the payment and/or mandate. This will be
// displayed to the payer when authorising the billing request.
Expand All @@ -1571,32 +1571,8 @@ export type BillingRequestTemplate = {
// from a list of your available schemes.
mandate_request_scheme?: string | null;

// Verification preference for the mandate. One of:
// <ul>
// <li>`minimum`: only verify if absolutely required, such as when part of
// scheme rules</li>
// <li>`recommended`: in addition to `minimum`, use the GoCardless payment
// intelligence solution to decide if a payer should be verified</li>
// <li>`when_available`: if verification mechanisms are available, use
// them</li>
// <li>`always`: as `when_available`, but fail to create the Billing Request
// if a mechanism isn't available</li>
// </ul>
//
// By default, all Billing Requests use the `recommended` verification
// preference. It uses GoCardless payment intelligence solution to determine
// if a payer is fraudulent or not. The verification mechanism is based on the
// response and the payer may be asked to verify themselves. If the feature is
// not available, `recommended` behaves like `minimum`.
//
// If you never wish to take advantage of our reduced risk products and
// Verified Mandates as they are released in new schemes, please use the
// `minimum` verification preference.
//
// See [Billing Requests: Creating Verified
// Mandates](https://developer.gocardless.com/getting-started/billing-requests/verified-mandates/)
// for more information.
mandate_request_verify?: `${BillingRequestTemplateMandateRequestVerify}`;
// Verification preference for the mandate.
mandate_request_verify?: string | null;

// 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.
Expand All @@ -1607,12 +1583,12 @@ export type BillingRequestTemplate = {
name?: string;

// Amount in full.
payment_request_amount?: string;
payment_request_amount?: string | null;

// [ISO 4217](https://en.wikipedia.org/wiki/ISO_4217#Active_codes) 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_currency?: string;
payment_request_currency?: string | null;

// A human-readable description of the payment and/or mandate. This will be
// displayed to the payer when authorising the billing request.
Expand Down Expand Up @@ -1647,13 +1623,6 @@ export type BillingRequestTemplateCreateRequestLinks = {
creditor?: string;
};

export enum BillingRequestTemplateMandateRequestVerify {
Minimum = 'minimum',
Recommended = 'recommended',
WhenAvailable = 'when_available',
Always = 'always',
}

/** Type for a billingrequesttemplatemandaterequestconstraints resource. */
export type BillingRequestTemplateMandateRequestConstraints = {
// The latest date at which payments can be taken, must occur after start_date
Expand Down
Loading