Curbstone Payment

What your customer experiences

Curbstone Payment is a redirect gateway. At the point of payment, the customer's browser leaves the Foxy checkout entirely and is sent to a page hosted by Curbstone — its "Payment Landing Page" — where they enter their card details. Once payment completes, Curbstone sends them back to finish on the Foxy receipt.

Two things follow from that:

• Foxy never sees or handles the card number. Card capture happens entirely on Curbstone's hosted page, not inside the Foxy checkout. That changes your PCI scope: your systems (and Foxy's checkout) never touch cardholder data for these transactions.

• You cannot restyle the payment page from Foxy. Because the customer is on a page Curbstone hosts and controls, Foxy's checkout templates, CSS and Twig customisations have no effect on it. If you need the payment step to match your storefront's look and feel, this is not the integration for that — that page's branding is Curbstone's to change, not yours.

Setting up Curbstone Payment

You need an existing Curbstone account before you start. Curbstone does not offer self-service onboarding — contact them at https://curbstone.com to get set up.

1. 1

   Ask your Curbstone representative for the two values Foxy needs: your Merchant ID and your Customer Code.

2. 2

   In the Foxy administration at https://admin.foxy.io, go to Settings > Payments.

3. 3

   Select the payment method set you want to use. If you only have one, it will be the Default Payment Method Set.

4. 4

   Click Add payment method + and choose Curbstone Payment.

5. 5

   Under Live setup, enter your Merchant ID.

6. 6

   Enter your Customer Code. This field is masked — use the reveal icon if you need to check what you typed.

7. 7

   Click Create to save the payment method.

That is the whole panel. There are only two fields, and there are no toggles, dropdowns or optional settings.

The panel is split into a Live setup block and a Test setup block carrying the same two fields. (The Live heading reads "Live setup (inactive)" while the payment method set has Use live credentials switched off — that reflects the current state of the set, not a different set of fields.)

Testing

Foxy provides shared test credentials for Curbstone Payment, so you can run test transactions without setting up your own sandbox account. Leave the Test setup fields as they are.

Those shared credentials only exercise the integration itself. If you need to test against your own Curbstone configuration — your own merchant codes, your own settlement behaviour — ask Curbstone for a test Merchant ID and Customer Code and enter those under Test setup instead.

Test card numbers

Curbstone does not publish test card numbers through Foxy. Ask your Curbstone representative which cards apply to your test account.

Important notes and caveats

• The customer leaves your checkout. This is a redirect gateway, not an embedded or iFrame payment step — see "What your customer experiences" above.

• Authorization-only is not supported. Curbstone Payment has no Authorize only (no capture) option in Foxy, so every transaction is authorized and captured together. If you need to authorize at checkout and capture later, this gateway cannot do it for you.

• Single currency. Multi-currency processing is not supported for this gateway in Foxy.

• No Foxy-side 3D Secure configuration. Foxy does not offer a 3D Secure setting for this gateway.

• Card verification is not configurable for this gateway in Foxy.

Troubleshooting

If a transaction is declined or returns a response code you do not recognise, contact Curbstone. They own the response code definitions for this platform and can see transaction detail that Foxy cannot.

If the payment method saves but transactions fail immediately, re-check the Merchant ID and Customer Code with Curbstone. Curbstone issues distinct merchant codes per location and business unit, so it is easy to be given a value that is valid but for the wrong unit.