Talk to us

Rehearse Aani connectivity

Short answer

Rehearse your bank’s Aani connection with TLS, your certificates, message signing and encryption. Check both a complete payment exchange and deliberate connection or security failures before production.

For integration, security and delivery teams.

Test checklist

  • Verify the hostname, port and route from the environment running the payment application.
  • Check certificate expiry, peer identity and the complete trust chain.
  • Where mTLS is required, verify client identity and the peer’s trust configuration.
  • Block and restore connectivity. Check timeouts, reconnection and pending work.
  • Check AMQP queues and REST endpoints, including deliberately incorrect destinations.
  • Send valid and invalid signatures and verify the expected acceptance or rejection.
  • Exercise the intended encryption configuration and a deliberately incorrect case.
  • Follow a complete payment and response. A successful TLS handshake alone is insufficient evidence.
  • Repeat after certificate or configuration changes and retain the settings and run record.

With PaySim

PaySim simulator exercises the bank’s Aani connection using TLS, certificates, message signing and encryption. It runs with synthetic data inside your environment and records each scenario run.

Scope

  • This rehearsal applies to the bank’s Aani connection. PaySim does not simulate Swift’s own infrastructure or PKI.
  • Official testing, certification and checks against the actual production endpoint remain part of your go-live plan.

Common questions

Can PaySim rehearse Aani certificates and message security?

Yes. Aani connectivity and security rehearsal exercises the bank's side using TLS connections and certificates, message signing and encryption against the simulator. Use synthetic payment data in the bank's own environment.

Is a TLS handshake enough to prove the connection works?

No. Also send a signed and encrypted message and check the response, routing and failure handling. A transport connection alone does not exercise the complete message exchange.

Should we include mTLS in the test plan?

Where your connection requires mTLS, check both sides' certificate requirements, identity checks and trust configuration. Follow the requirements for the connection you will actually use.

Does this cover Swift's PKI or SWIFT certificate testing?

No. PaySim does not simulate Swift's own infrastructure or PKI. For SWIFT, use the applicable official testing route for those checks; PaySim covers CBPR+ messaging and counterparty simulation.

Related guides

Last reviewed:

Discuss your test plan.