Entry
Deliver in EUR to a SEPA IBAN a payment that originated outside SEPA
BetaCross-border entry is a beta feature. It is enabled per account. To activate it, contact us.
What it is and when to use it
Entry lets you deliver, in euros, to a bank account in the SEPA area a payment that started outside SEPA. Your customer pays from abroad; Devengo delivers the EUR amount to the recipient's IBAN in Europe.
Use Entry when someone outside SEPA has paid and the money has to reach a SEPA account in euros. For example, a person in New York sends money to a relative in Spain: you receive the international payment and Devengo delivers the euros to the relative's Spanish IBAN.
Four parties take part in every Entry payment:
| Party | Role |
|---|---|
| Original sender | The person or company outside SEPA who ordered the payment. |
| You | Devengo's customer. You received the international payment and fund the EUR delivery from your Devengo account. |
| Devengo | Debits your account and sends the payment to the recipient's bank. |
| Recipient | The person or company who receives the euros in a SEPA account. |
You and the original sender are often different parties. A single Devengo account can fund payments for many senders, but each payment always carries the details of the person who really ordered it.
To pay a recipient whose account is outside SEPA, see Exit. That direction is still a draft.
How it works
- The original sender pays you from outside SEPA, through your usual channel.
- If that payment was in another currency, you convert it to euros. Devengo does not do currency conversion.
- You send Devengo the instruction: the EUR amount, the recipient's IBAN and who originally paid.
- Devengo debits the amount from your Devengo account and sends the payment to the recipient's bank.
- You are notified as the payment progresses, until it reaches its final outcome.
What you need to provide
Each Entry payment carries the SEPA delivery plus the story of the original international payment.
| Information | What it is | Required |
|---|---|---|
amount | The amount to deliver, always in euros. | Yes |
recipient and destination | Name and SEPA IBAN of the person or company receiving the funds. | Yes |
description | Text shown on the recipient's account statement. | Yes |
sender | Name, city and country, and the account of who really ordered the payment. The bank BIC goes in account.bank.bic. | Yes |
uetr | The unique reference of the original international payment. | Yes |
non_euro_leg_debited_at | When the original sender was charged, outside SEPA. | Yes |
original_amount and exchange_rate | The amount in its original currency and the rate you applied. For information only: Devengo always delivers the EUR amount. The rate is needed whenever the original amount is not in euros. | No |
The sender's address has two fields, city and country. Both are required. The example uses account_number as id_scheme. iban is also accepted.
Example
In practice, step 3 is a single API call. company_reference is optional. This request shows the information it carries:
{
"account_id": "acc_8AnWmtBGh0ZeBzjM3nYqRS",
"company_reference": "123",
"description": "Payment from John Smith",
"recipient": "Ana Devenger",
"destination": { "type": "iban", "iban": "ES9121000418450200051332" },
"amount": { "cents": 10000, "currency": "EUR" },
"uetr": "b3f1c2a0-7e4d-4c1a-9f2e-1a2b3c4d5e6f",
"non_euro_leg_debited_at": "2026-11-05T08:30:00Z",
"sender": {
"name": "John Smith",
"address": { "city": "New York", "country": "us" },
"account": {
"id_scheme": "account_number",
"id": "ACCOUNT-9981",
"issuer": "ACMEPAY",
"bank": { "bic": "CHASUS33XXX" }
}
},
"original_amount": { "cents": 11500, "currency": "USD" },
"exchange_rate": "0.8696"
}In plain words: deliver 100.00 EUR from your Devengo account to Ana Devenger's Spanish IBAN, on behalf of John Smith in New York, who originally paid 115.00 USD, converted at 0.8696. The full request is in Create cross-border entry payment.
Outcomes
An entry payment is a Devengo payment (pyo_… id). These payments do not appear in GET /v1/payments, and GET /v1/payments/{id} returns 404 for their ids. Read them with GET /v1/payments/cross_border and GET /v1/payments/cross_border/{id}. Use direction to tell entry and exit apart.
Entry payments use the same payment statuses as other payments. Every entry payment ends in one of two outcomes:
| Outcome | What it means |
|---|---|
confirmed | The funds are available in the recipient's SEPA account. |
rejected | The payment could not be delivered. The amount is not debited from your account, or is returned to it, and you are told why. |
Scope and getting started
In this beta, Entry covers delivery in euros to SEPA accounts. The same amount limits as regular Devengo payments apply.
Until cross-border entry is enabled for your company, the endpoint returns 404 in production. Without the product, it returns 403 with code product_not_active. The endpoint is available from API version 202611.
Not included yet:
- Currency conversion: you convert to euros before sending the payment.
- Payment previews and payment receipts.
- A return after confirmation (
reversed), recalls and investigations. - Verification of Payee (
vop_id). - Automatic retries. Entry payments are not retried by the Smart Retry System.
To get started:
- Contact us to activate cross-border entry for your company.
- Tell us which Devengo account will fund the payments, so we can enable it.
- Test the flow in the sandbox before going live. The destination IBAN decides the simulated result. Entry uses the same reserved IBANs as payments, listed in Sandbox → Test Data. Any other valid SEPA IBAN results in
confirmed.
Updated about 12 hours ago