International Payment body fields

Below is a description of all fields available in the POST /v2/payments request body for international payments.

Required fields must be provided to successfully create a payment.

Field	Type	Required	Description
batchId	string	No	Partner's internal reference for the payment. Must be unique per payment or left empty. Used to ensure the same payment is not created twice.
amount	decimal	Yes	Amount to be transferred to the recipient.
senderBankAccount	string	Yes	The bank account from which the amount will be debited – i.e., the November First customer’s account. Requires an active Overførselsservice agreement for auto-initiation.
fromCurrencyCode	string	Yes	The currency code of the source account (must match the sender bank account currency).
toCurrencyCode	string	Yes	The currency code in which the recipient should receive the amount.
side	string	Yes	Indicates whether the amount is specified as a Buy or Sell order. Use Buy if you want to buy the recipient currency amount; use Sell if selling the source currency.
feeType	int	Yes	Specifies how international transfer fees are handled: 0 = Shared costs (sender and recipient share costs, default); 1 = Sender pays all (recipient receives full amount).
recipientName	string	Yes	Recipient’s name.
recipientAddress	object	No	Recipient’s address. If provided, subfields (e.g., street, postalCode, city, country) must follow the standard described in the documentation.
recipientAccountNumber	string	Yes	Recipient’s IBAN, or account number if the destination country does not use IBAN.
recipientBic	string	Yes	BIC (SWIFT) code for the recipient’s bank.
recipientEmail	string	No	Recipient’s email address. If provided, a payment receipt will be sent to the recipient.
message	string	No	Message sent with the payment, visible to the recipient in their bank account.
dueDate	date (YYYY-MM-DD)	Yes	Date on which the payment must be executed. Must be a valid banking day.
webHookURL	string	No	URL for receiving real-time updates and changes related to the payment. If not provided, the partner’s default webhook (if configured) will be used.
externalPartnerUserName	string	No	Partner’s internal reference to the user in their system who created the payment.
invoiceNumber	string	No	Invoice or receipt number for the payment.

Example Request – International Payment

JSON

{
  "batchId": "INTL-2025-001",
  "fromCurrencyCode": "DKK",
  "toCurrencyCode": "EUR",
  "side": "Buy",
  "feeType": 1,
  "amount": 2500.00,
  "dueDate": "2025-09-15",
  "senderBankAccount": "12345678901234",
  "recipientName": "Der Deutsche Lieferant Gmbh",
  "recipientAddress": {
    "street": "Street1",
    "street2": "Street2",
    "postalCode": "1232",
    "city": "Berlin",
    "countryCode": "DE",
    "country": "Germany"
  },
  "recipientAccountNumber": "DE89370400440532013000",
  "recipientBic": "TRSYDEFFXXX",
  "recipientEmail": "[email protected]",
  "message": "Invoice INTL-2025-001",
  "webHookURL": "https://partner.example.com/webhook",
  "externalPartnerUserName": "api-intl-user-1",
  "invoiceNumber": "INTL-INV-2025-09-001"
}