com.worldline.connect.sdk.java.v1.domain

Class CashPaymentProduct1503SpecificInput

java.lang.Object

com.worldline.connect.sdk.java.v1.domain.CashPaymentProduct1503SpecificInput

Deprecated.

No replacement

@Deprecated
public class CashPaymentProduct1503SpecificInput
extends Object

Constructor Summary

Constructors

Constructor and Description
CashPaymentProduct1503SpecificInput() Deprecated.

Method Summary

Modifier and Type	Method and Description
String	getReturnUrl() Deprecated. No replacement, since Boleto Bancario no longer needs a return URL
void	setReturnUrl(String value) Deprecated. No replacement, since Boleto Bancario no longer needs a return URL

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

CashPaymentProduct1503SpecificInput

public CashPaymentProduct1503SpecificInput()

Deprecated.

Method Detail

getReturnUrl

@Deprecated
public String getReturnUrl()

Deprecated. No replacement, since Boleto Bancario no longer needs a return URL

The URL that the customer is redirect to after the payment flow has finished. You can add any number of key value pairs in the query string that, for instance help you to identify the customer when they return to your site. Please note that we will also append some additional key value pairs that will also help you with this identification process.
Note: The provided URL should be absolute and contain the protocol to use, e.g. http:// or https://. For use on mobile devices a custom protocol can be used in the form of protocol://. This protocol must be registered on the device first.
URLs without a protocol will be rejected.

setReturnUrl

@Deprecated
public void setReturnUrl(String value)

Deprecated. No replacement, since Boleto Bancario no longer needs a return URL

The URL that the customer is redirect to after the payment flow has finished. You can add any number of key value pairs in the query string that, for instance help you to identify the customer when they return to your site. Please note that we will also append some additional key value pairs that will also help you with this identification process.
Note: The provided URL should be absolute and contain the protocol to use, e.g. http:// or https://. For use on mobile devices a custom protocol can be used in the form of protocol://. This protocol must be registered on the device first.
URLs without a protocol will be rejected.