Payment Profiles

A payment profile determines which payment methods a merchant can use on their checkout. Each merchant requires at minimum one payment profile but can use multiple to cover different use cases.

Required Information for Payment Profiles

The following information is required for each payment profile:

  • Accepted payment methods: card, open banking, sepa, sepa direct debit, ideal, vipps
  • For card and vipps payment methods: CaptureMode (manual or instant)

Additional Configurations for Card Payments

Payment Contract Types

  • One-off: For single payments of immediate purchases
  • Recurring: For payments at regular intervals using the same amounts (e.g., subscriptions) including trial periods with future recurring charges
  • Unscheduled Charge: For ad-hoc payments (e.g., top-up of account balance)

Card Auth Types

  • Pre-auth: For reserving funds on a card before the final amount is known
  • Final-auth: For capturing the full payment amount
  • Account status: For checking the validity of a card without reserving funds. This can be used for:
    • Card verification before future payments
    • Saving payment methods for later use
    • Setting up trial periods that convert to paid subscriptions

Card Capture Modes

  • Instant: Automatically capturing the full amount of the authorization
  • Manual: Manually capturing partial or full amount of the authorization later

Wallet Types

  • Google Pay
  • Apple Pay

Where applicable, a payment profile will also contain a card configuration which includes information about 3D Secure and supported wallet types.

Capture mode might not be supported by all payment methods. For example, card payments can be captured instantly or manually, while open-banking payments are captured instantly only.

Statement Descriptor

The statement descriptor is text that appears on the cardholder's statement, providing additional information about the payment, such as the merchant name. By default, it is set to FNG*Merchant Name.

A custom Statement descriptor can be set per payment profile using the "Dynamic descriptor" field. The text should be 5-18 characters long and can only contain alphanumeric characters and spaces.

Statement descriptor is only supported for card payments.

Creating a Payment Profile

For more information on how to create or update a payment profile, see the API reference.