This site requires javascript to be enabled.

RuPay Credit Skip to main content
Worldline Connect Home Page
Global Collect (Connect)
Other Worldline developer portals

Results for

Results for Searching
  1. Home
  2. Payment methods
  3. RuPay Credit

RuPay Credit

Only available on TechProcess platform

Process flows

In order to integrate RuPay (Credit & Debit), please refer to our API Reference.

RuPay transaction states

Create refund Create capture Create hosted checkout Create payment

  • CREATED – initial state of a transaction. If a transaction remains in this state, it indicates a problem.
  • REDIRECTED – we have provided the redirect details and are waiting for the consumer to complete the payment. If this state persists, it means we haven't retrieved the final status from the bank yet. Successful payments will resolve automatically.
  • PENDING APPROVAL – the transaction is awaiting your approval to capture the funds. This applies to transactions requiring manual merchant approval before processing.
  • CAPTURED – the transaction was completed successfully, and we have received confirmation that the funds are on their way.
  • PAID – we have collected the funds and will begin the remittance process to you.
  • CHARGEBACKED – the payment was disputed by a consumer and reversed. This is a final state indicating the funds have been returned to the consumer.
  • REFUND REQUESTED – the payment refund was requested by the consumer.
  • REFUNDED – This is a final state indicating the funds have been refunded to the consumer.
  • REJECTED – the transaction was rejected by either us or the bank. This is the final state.
  • CANCELLED – the transaction was canceled by either you or the consumer. This is the final state.
  • REJECTED CAPTURE – the capture request was rejected by us or the acquiring bank. This is a final state for the capture attempt.

Payment flow

RuPay Credit.png

  1. The consumer selects a card payment product and makes a transaction with you.
  2. Your server sends the authorization request to us containing the card payment details of the consumer and your reference ID. 
  3. Before authorizing the transaction we first send the transaction for authentication
  4. If authentication is completed, the transaction continues
  5. We redirect the authorization request to the relevant acquiring channel.
  6. The acquirer redirects the authorization request to the card issuing bank.
  7. The card issuing bank processes the transaction in real-time, returning an authorization or decline response.
  8. The acquirer sends the authorization result to us.
  9. We return the request response result to you - If the request is authorized, you can choose to release the product or service to the consumer.
  10. We will also, automatically or after a request for capture, send the settlement file to the acquirer to facilitate collection of a successfully authorized transaction.
  11. The acquirer sends the settlement request, via the card scheme, to the card issuing bank and the consumer‘s account will be debited accordingly.
  12. The card issuing bank transfers, via the card scheme, the funds to the acquirer.
  13. The acquirer transfers the funds to our bank account where the confirmation of funds is registered.
  14. You will then receive the funds and a payment report which will include your payment reference – This enables you to update the relevant orders based on the information contained in the report.

During the transaction process the payment status is updated each time a request or response is received and the changes are reported to your system. 

Next Testing