Merge pull request #340 from getlago/bank-transfers

update openapi for Bank Transfers payment method
getlago · Feb 21, 2025 · 788ff93 · 788ff93
2 parents 136bca1 + 50a1099
commit 788ff93
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 7 deletions.
diff --git a/openapi.yaml b/openapi.yaml
diff --git a/src/schemas/CustomerBillingConfiguration.yaml b/src/schemas/CustomerBillingConfiguration.yaml
@@ -40,7 +40,7 @@ properties:
     nullable: true
     items:
       type: string
-    description: Specifies the available payment methods that can be used for this customer when `payment_provider` is set to `stripe`. The `provider_payment_methods` field is an array that allows multiple payment options to be defined. If this field is not explicitly set, the payment methods will be set to `card`. For now, possible values are `card`, `sepa_debit`, `us_bank_account`, `bacs_debit`, `boleto`, `link` and `crypto`. Note that when `link` is selected, `card` should also be provided in the array.
+    description: Specifies the available payment methods that can be used for this customer when `payment_provider` is set to `stripe`. The `provider_payment_methods` field is an array that allows multiple payment options to be defined. If this field is not explicitly set, the payment methods will be set to `card`. For now, possible values are `card`, `sepa_debit`, `us_bank_account`, `bacs_debit`, `boleto`, `link`, `crypto` and `customer_balance`. Note that when `link` is selected, `card` should also be provided in the array. When `customer_balance` is selected, no other payment can be selected.
     example:
       - card
       - sepa_debit
@@ -49,3 +49,4 @@ properties:
       - link
       - boleto
       - crypto
+      - customer_balance