PayPaga
  1. Pay In - Direct API Integration
PayPaga
  • Introduction
    • Introduction
    • API Reference
    • Errors
    • Standard Codes and Values
  • Authorization
    • Authorization
    • OAuth 2.0 Token Generation
  • Pay In - Direct API Integration
    • Pay In - Direct API Integration
    • Pay In - Payment Options
      POST
    • Pay In - Payment Processing
      POST
    • Pay In - Query Transactions
      GET
  • Pay In - PayURL Integration
    • Pay In - PayURL Integration
    • Pay In - Create PayURL
  • Pay Out - Direct API Integration
    • Pay Out - Direct API Integration
    • Pay Out - Query Transactions
    • Pay Out - Payment Processing
  • Pay Out - Examples
    • Pay Out - Brazil
    • Pay Out - Mexico
    • Pay Out - Argentina (V2)
    • Pay Out - Colombia (V2)
    • Pay Out - Ecuador (V2)
    • Pay Out - Guatemala (V2)
    • Pay Out - Peru (V2)
  • Transactions Status Notification
    • Transactions Status Notification
  • Query Balance
    • Query Balance
  • Appendix
    • Transaction Status Definitions and Lifecycle
  1. Pay In - Direct API Integration

Pay In - Direct API Integration

An advanced workflow designed for customised integrations where the merchant will manage the complete consumer experience leveraging a backend integration for the transaction processing. The workflow steps are listed below and illustrated in the sequence diagram.
1.
Prior to any transaction processing the Merchant must configure a Notification Method in the Developer's section of the Merchant Portal for the corresponding environment to enable transaction lifecycles notifications.
2.
Call OAuth 2.0 Token Generation and retrieve OAuth2.0 token
3.
Using the OAuth2.0 token, the Merchant will interact with PayPaga API in two steps per transaction as follows:
Call the Pay In - Payment Options request to retrieve the current selection of orchestrated Payment Methods with corresponding data requirements.
Call the Pay In - Payment Processing request with selected Payment Method, supplying any Payment Method specific data.
4.
Action payment lifecycle notifications sent to the registered notification method.
v1_pay_in_flow.png
Previous
OAuth 2.0 Token Generation
Next
Pay In - Payment Options
Built with