Skip to main content
POST
Create a payment method

Authorizations

Authorization
string
header
required

Body

multipart/form-data
type
enum<string>
required

Type of payment method to create. Only mx_direct_debit is supported.

Available options:
mx_direct_debit
Example:

"mx_direct_debit"

customer
string
required

Unique identifier of the customer the payment method belongs to.

Example:

"cus_0ujsswThIGTUYm2K8FjOOfXtY1K"

mx_direct_debit
object
required

Terms of the direct debit mandate.

Response

The payment method Fintoc created for the mandate. The payment method's mx_direct_debit status is pending until the account holder authorizes the mandate with their bank.

A payment method represents a customer's stored payment instrument, ready to be charged without the customer going through the full authorization flow again. The shape of the object depends on its type: the type-specific details live under a key named after the type (bank_transfer, card, mx_direct_debit, or pac).

id
string
required

Unique identifier of the payment method.

Example:

"pm_1zXcVbNmAsDfGhJk"

object
any
required

Type of the object. Always payment_method.

bank_transfer
object | null
required

Details of the linked bank account that pays the transfers. null when the linked account backing the payment method is no longer available.

created_at
string<date-time>
required

ISO 8601 timestamp of when the payment method was created.

Example:

"2026-01-15T14:30:00.000Z"

customer
string
required

Unique identifier of the customer the payment method belongs to.

Example:

"cus_oVgVqlnK0PdmGirH"

mode
enum<string>
required

Mode of the payment method. live payment methods charge real money; test payment methods use fake data for integration testing.

Available options:
live,
test
Example:

"live"

type
any
required

Type of the payment method. Always bank_transfer.