Message Queue Authentication

Overview

Connect to Newline’s Message Queue (MQ) by authenticating with the credentials provided during onboarding and selecting a supported protocol. Configure SSL/TLS for every connection.

Credentials

After defining your subscription topics, Newline will issue:

  • Username and Password: Used to authenticate your MQ connection.
  • Topic Prefixes: Required for topic subscription formatting.
  • Host and Port Details: Based on your selected protocol.

Connection Requirements

Configure every MQ connection to:

  • Use SSL/TLS encryption.
  • Connect to the appropriate sandbox or production endpoint.
  • Include protocol-specific headers, such as client-id and subscriptionName for STOMP.

Sandbox Endpoints

Use these endpoints for testing in the sandbox environment:

ProtocolEndpoint
OpenWiressl://mq-sandbox.newline53.com:61617
AMQPamqp+ssl://mq-sandbox.newline53.com:5671
STOMPstomp+ssl://mq-sandbox.newline53.com:61614
MQTTmqtt+ssl://mq-sandbox.newline53.com:8883
WSSwss://mq-sandbox.newline53.com:61619

Production Endpoints

Use these endpoints for live production traffic:

ProtocolEndpoint
OpenWiressl://mq.newline53.com:61617
AMQPamqp+ssl://mq.newline53.com:5671
STOMPstomp+ssl://mq.newline53.com:61614
MQTTmqtt+ssl://mq.newline53.com:8883
WSSwss://mq.newline53.com:61619

Implementation Tips

  • Confirm that your client supports the selected protocol and SSL/TLS.
  • Use durable subscriptions to support recovery after interruptions.
  • Include client-id and subscriptionName headers when using STOMP.
  • Continue processing RTP transfer events when a transfer enters a queued state, until you receive a final transfer status or settlement event.

Additional Resources

For queue testing scenarios, sandbox behavior, queue lifecycle processing, and queued payment examples, see:

MQ Behavior in Sandbox & Production


Did this page help you?