{"templateId":"openapi_docs","versions":[{"version":"v1","label":"v1","link":"/api-reference/v1/customers","default":false,"active":true,"folderId":"1b9c9f54"},{"version":"v2","label":"v2","link":"/api-reference/customers","default":true,"active":false,"folderId":"1b9c9f54"}],"sharedDataIds":{"openAPIDocsStore":"oas-api-reference/@v1/index.yaml","sidebar":"sidebar-sidebar.yaml__api-reference_v1"},"props":{"definitionId":"api-reference/@v1/index.yaml","dynamicMarkdocComponents":[],"baseSlug":"/api-reference/v1","seo":{"title":"Customers","siteUrl":"https://developer.flute.com","description":"\nCustomers are entities used to organize and manage saved payment methods.\nThese include billing details, transaction history, and recurring payments.\nA customer record may contain their name, email address, phone number, and billing or shipping addresses.\nHaving a customer association is not required to pay for transactions.      \n\nCustomers may pay transactions in one of three ways:\n* Vaulted payments\n* Standalone tokenization, also known as orphan vaulted payment\n* Account supported\n\n**Vaulted payments**<br>\nA vaulted payment method is a securely stored payment credential.\nCustomers can be associated with one or more vaulted payment methods.\nThis applies to credit card or bank account payments.\n\nThis is considered a more secure method rather than storing the card number directly.\nThat information has previously been tokenized and saved for future use.\nVaulted information can be safely accessed through a payment identifier.\nThis is typically used for recurring billing, subscriptions, saved checkout experiences, and card-on-file transactions.\n\nIn the transaction payment, the field `customerId` is provided.\nThe customer's vaulted payment methods are available for selection.\n\n**Standalone tokenization**<br>\nClients may use standalone tokenization, also known as an orphan vaulted payment.\nThis allows a payment method to be vaulted even when the payer has not been recognized as a customer entity.\nThe transaction proceeds using a previously established payment method identifier.\n\nStandalone tokenization is useful when a payment method must be vaulted before a customer profile exists.\nThis includes guest checkouts, delayed onboarding, account setup, or card-on-file collection before registration is complete.\n\nIn the transaction payment, the field `customerId` is omitted but `paymentMethodId` is provided.\nThis indicates the merchant's orphan vaulted payment method is used.\n\n**Account Supported**<br>\nClients may use accounts supporting orphan payments.\nThis is a form of a payment method that temporarily exists without a customer association.\n\nIn the transaction payment, both fields `customerId` and `paymentMethodId` are omitted.\nThe transaction uses the credit or debit card, or bank account data supplied in the request.\n","lang":"en-US","llmstxt":{"hide":true,"excludeFiles":[]}},"itemId":"customers","disableAutoScroll":true,"metadata":{"subType":"openapi-operation"},"compilationErrors":[],"markdown":{"partials":{},"variables":{"rbac":{"teams":["anonymous"]},"user":{},"remoteAddr":{"hostname":"developer.uat.flute.com","port":4000,"ipAddress":"216.73.217.69"},"lang":"default_locale","env":{"PUBLIC_REDOCLY_BRANCH_NAME":"main"}}},"pagePropGetterError":{"message":"","name":""}},"slug":"/api-reference/v1/customers","userData":{"isAuthenticated":false,"teams":["anonymous"]},"isPublic":true}