202611 API Version: Cross-border payments and new counterparty operating modes

Cross-border payments are here! Our new API, now in beta, connects SEPA with the rest of the world, letting you receive payments from outside SEPA and pay recipients beyond it. Plus, counterparty operating modes are now enforced on payments.

Cross-border payments (beta)

  • Cross-border payments, available in sandbox on request:
    • POST /v1/payments/cross_border/entry: deliver in EUR to a SEPA IBAN a payment that originated outside SEPA.
    • POST /v1/payments/cross_border/exit: pay, with EUR funds, a recipient whose account is outside SEPA. This direction is provisional and may change.
    • GET /v1/payments/cross_border and GET /v1/payments/cross_border/{id}: read cross-border payments.
  • New guides: Cross-border entry and Cross-border exit.

Counterparty operating modes

Mandatory and restrictive counterparty operating modes are now enforced on create payment and preview payment:

  • Mandatory — payments must reference a counterparty_id. Requests with inline destination and recipient are rejected with 404 mandatory_counterparty.
  • Restrictive — payments must reference a verified counterparty. Requests without a counterparty_id, or referencing an unverified counterparty, are rejected with 404 unverify_counterparty.

Optional mode remains the default and its behaviour is unchanged. The operating mode is set by Devengo for each integration; contact your Devengo representative if you are unsure which mode applies to you.