What authentication does the Interac e-Transfer API use?

The API uses OAuth 2.0 bearer token authentication. You obtain a token through J.P. Morgan's identity service and include it in the Authorization header. Through Jentic, the OAuth credentials and token refresh are handled automatically in your Jentic One instance.

Can I send payments 24/7 with the Interac e-Transfer API?

Yes. Interac e-Transfer operates 24/7/365 for domestic Canadian dollar payments. Unlike wire transfers or ACH which have banking-hour restrictions, e-Transfers process in real-time regardless of time or day. Recipients can deposit funds immediately through their banking app.

What recipient identification methods are supported?

The API supports three recipient identification methods: email address, phone number, or direct bank account details. Email and phone-based transfers require the recipient to accept and deposit the funds. Bank account-based transfers route directly to the specified account without recipient action.

How do I initiate an e-Transfer payment through Jentic?

Search Jentic for 'send an Interac e-Transfer' to find the POST /tsapi/v1/payments operation. Jentic returns the input schema showing required fields like amount, currency (CAD), recipient email or phone, and payment type. Execute through Jentic and the payment is submitted to J.P. Morgan's treasury platform. Install with pip install jentic.

Can I limit what my agent is allowed to do with the Interac e-Transfer API?

Yes. Because you run Jentic One yourself, you decide which operations and credentials your agent may use, so no call runs beyond the set you allow. The Interac e-Transfer API exposes a single payment operation, POST /tsapi/v1/payments for initiating a CAD transfer, and you can grant your agent only that operation while withholding your J.P. Morgan bearer token from its prompt and logs. Since the payment details ride in the request body, your own rules govern exactly which recipients and amounts the agent can submit.