What authentication does the MobilePay API use?

The API uses an API key passed in the Authorization header. Generate the key from the Mobeco merchant portal and include it on every request. Through Jentic the key is stored in the credential vault and injected at execution time so agent code never sees the raw value.

Can I issue partial refunds with the MobilePay API?

Yes. POST /refunds takes the original payment ID and a refund amount that may be smaller than the original charge. The refund is returned to the customer's MobilePay account and reconciled against the original payment.

What are the rate limits for the MobilePay API?

Mobeco applies per-merchant rate limits on payment creation and refund issuance to protect against abuse. Status lookups have higher quotas than write calls. Coordinate with Mobeco support for current numeric limits before high-volume promotions.

How do I create a payment through Jentic?

Search Jentic for create mobilepay payment, load the schema for POST /payments, and execute with the order amount in DKK and a merchant order reference. The response includes the payment ID and a status to poll.

Does the MobilePay API cover other Nordic countries?

This API surface targets the Danish MobilePay product. For Norwegian, Finnish, or other Nordic mobile-payment products, use the country-specific API for that market rather than the Mobeco endpoints.

Can I limit what my agent is allowed to do with the MobilePay API?

Yes. Because you run Jentic One yourself, your own rules decide which of the MobilePay operations the agent may call, so you can let it create a payment (POST /payments) and check status (GET /payments/{id}) while leaving refunds (POST /refunds) out unless you add them. Since the payment ID sits in the URL path, a rule can also pin the agent to reading a single payment rather than any status lookup. Your API key is held by your own instance and injected at execution time, so the agent only invokes the operations you permit and never handles the raw Authorization value.