Get provider redirect details.

Returns HTML content suitable for use in redirecting a customer's browser to a PSP for collection of payment details.
Response Code | Fault Code | Fault | Suggested User Message
------------- | ---------- | ----- | ----------------------
400 | 90000 | InsufficientDataFault | Additional data required
400 | 90065 | UnavailableProviderFault | Payment Provider cannot complete transaction
400 | 90021 | InvalidDigestFault | Provided Digest is incorrect
404 | 90071 | UnknownProviderFault | Requested provider Is unknown
500 | 90061 | SystemFailureFault | System Failure, please try again later
404 | 90070 | UnknownMerchantFault | Merchant does not exist

Path Params
uuid
required

The ID of the customer who is owner of payment method

Body Params

Information required for redirecting to provider.

string
required
length ≤ 30

Payment provider

string
required
length ≤ 100

Merchant code

string
required

Uuid used to calculate digest

string
required

Hashed request details

data
array of objects
required

Additional information about the payment method to be passed to the PSP. This may be PSP specific data that is required to generate the redirect URL.
For 3DS2 enabled PSPs, certain customer details may be passed in the request to maximise the chance of a frictionless transaction. The following elements can be passed as key-values in the data element. They will be used in the request instead of the values stored against the customer in Subscriber Management.

  • 3DSEmail
  • 3DSAddressLine1
  • 3DSAddressLine2
  • 3DSAddressLine3
  • 3DSCity
  • 3DSPostcode
  • 3DSCountryCode

Setting these values will not update the data stored against the customer.

data*
Headers
string

The tenant ID for which the operation is being carried out. This will be automatically generated during the authentication process.

string

The ID of a user who is performing the operation. This will be automatically generated during the authentication process.

string

The source of whether records are updated by HMAC or a USER. This will be automatically generated during the authentication process. For customers accessing the service the source will be set to CUSTOMER.

Responses

Language
URL
Choose an example:
application/json