This local demo shows the three integration styles clients care about most: hosted payin creation, S2S payin orchestration, and transaction lookup. It is designed to be understandable for both engineering teams and implementation managers.
Payyd URL: {{ transaction.get('payydUrl') }}
{% endif %} {% if transaction.get('thirdPartyCheckOutUrl') %}Hosted checkout URL: {{ transaction.get('thirdPartyCheckOutUrl') }}
{% endif %} {% else %}The lookup completed, but the SDK response did not contain a transaction object. The full response is shown below.
{% endif %}{{ response_payload_json }}
Use the forms below to create and inspect transactions. The highlighted pill shows the most recently used flow.
Create a hosted checkout session and redirect the customer to the Payyd URL returned by the API.
Create the S2S transaction shell before collecting sender details and payment method information.
Use the merchant reference to inspect the latest state of a hosted payin transaction.
Only fields required for the selected country, entity type, and payment method are shown.
{% if s2s_options_error_message %}Could not load country payment/ID options automatically: {{ s2s_options_error_message }}
{% endif %}These details are useful for engineering validation and troubleshooting. Client-facing users can ignore this section.
{{ response_payload_json }}